The docs of Neo4j state that when running in HA mode, you get eventual consistency. This is a quote from that page:
All updates will however propagate from the master to other slaves eventually so a write from one slave may not be immediately visible on all other slaves
My question is: is there a configuration that will allow me to write a cluster with strong consistency, of course at the cost of reduced performance? I'm looking for some sort of active-passive failover cluster configuration.
There is such an config option.
ha.tx_push_factor
determines to how many slaves a transaction should be pushed to synchronously. When setting this toha.tx_push_factor=<clustersize>-1
you have immediate full consistency.