Property set using rest api sometimes doesn't take into effect

[Vishal Shah]

Anybody else has had individual properties set using rest api sometimes sometimes doesn't take into effect? It only happens sometimes. We run in a HA environment. Anybody have any ideas? We are on Neo4j 2.1.3 enterprise on CentOS

Thanks!

[Michael Hunger]

How do you see that? Any error messages? Deadlocks? What does the response look like in such cases?

Are you writing to master or slaves?

Am 18.04.2015 um 16:41 schrieb Vishal Shah <gol...@gmail.com>:

Anybody else has had individual properties set using rest api sometimes sometimes doesn't take into effect? It only happens sometimes. We run in a HA environment. Anybody have any ideas? We are on Neo4j 2.1.3 enterprise on CentOS

Thanks!

--
You received this message because you are subscribed to the Google Groups "Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Vishal Shah]

Writing to slaves. The response always is a 2xx success.

[V Shah]

Sorry we write to a LB  that covers neo4j master and slaves (2).

[Michael Hunger]

Does it write to all the same request? Or does it direct writes to master?

Perhaps the property updated is only delayed by the slave's pull interval to show up on the slave?

Michael