Cannot start kernel since there are no other nodes in the cluster to sync up for the database system

[Jacobus Geluk]

I'm getting this message after stopping (and killing one of) the nodes in the cluster:

Cannot start kernel since there are no other nodes in the cluster to sync up for the database system

What does this mean? This doesn't make sense to me, the first node in the cluster can be any node right? There's no such thing as a leader-node when everything is down?

[Michael Grove]

The message is a bit misleading, it just means that it couldnt obtain a node to sync with.  It could be the case that the node you just stopped had not yet completed shutdown and the node you were trying to add selected the node being shut down as the one to sync from, which subsequently finished shutting down and resulted in that message.  There's also a bit of lag time for the znodes to disappear from ZK.

We'll investigate this a bit to see if we can reproduce, but generally, you might just wait a minute between shut down and restart to let the node complete the shutdown process and ZK to propagate the updates within the ensemble.

Cheers,

Mike

 

--
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to
stardog+u...@clarkparsia.com
For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en