On 8/6/2013 1:56 PM, Erick Erickson wrote:
I've become aware of a situation I thought I'd pass along. A SolrCloud
installation had several ZK nodes that has very significantly offset
times. They were being hit with the "ClusterState says we are the
leader, but locally we don't think we are" error when nodes were
recovering. Of course whether this problem is now taken care of with
recent Solr releases (I haven't seen this go by the user's list for
quite a while) I don't quite know.
When the times were coordinated, many of the problems with recovery went
away. We're trying to reconstruct the scenario from memory, but it
prompted me to pass the incident in case it sparked any thoughts.
Specifically, I wonder if there's anything that comes to mind if the ZK
nodes are significantly out of synch with each other time-wise.
Does this mean that ntp or other strict time synchronization is
important for SolrCloud? I strive for this anyway, just to ensure that
when I'm researching log files between two machines that I can match
things up properly.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
