Hi there,
I talked to Chris Gioran and got the following diagnostics:
This* is
what happens when in a quorum of 2 ZK instances one goes down.
(*this == the remaining ZK instance - which is not in standalone mode
- will refuse to accept requests, hence the ZooClient in neo will barf
and die).
Thanks a lot, Peter.
I found another way to bring it up again,
As I thought there should be some incorrect status stored in the graph,
maybe start up the master instance in Non-HA mode can rectify the status. I
tried and that works. Now the HA cluster is running normally.
However, to prevent it
Nice,
glad it worked out!
Cheers,
/peter neubauer
G: neubauer.peter
S: peter.neubauer
P: +46 704 106975
L: http://www.linkedin.com/in/neubauer
T: @peterneubauer
Neo4j 1.6 released - dzone.com/6S4K
The Neo4j Heroku Challenge - http://neo4j-challenge.herokuapp.com/
On
3 matches
Mail list logo