Gregory Chanan created SOLR-5993:
------------------------------------
Summary: ZkController can warn about shard leader conflict after
conflict resolved
Key: SOLR-5993
URL: https://issues.apache.org/jira/browse/SOLR-5993
Project: Solr
Issue Type: Bug
Components: SolrCloud
Affects Versions: 4.7.1, 4.8, 5.0
Reporter: Gregory Chanan
Priority: Trivial
If the clusterState and ZK disagree about the shard leader for awhile, a
warning is printed to the log here:
{code}
String warnMsg = String.format(Locale.ENGLISH, "Still seeing
conflicting information about the leader "
+ "of shard %s for collection %s after %d seconds; our state says
%s, but ZooKeeper says %s",
cloudDesc.getShardId(), collection, tries, clusterStateLeaderUrl,
leaderUrl);
{code}
The issue is that the clusterStateLeaderUrl and leaderUrl are updated but not
checked before the warning, so a warning can be printed to the log saying
something like:
our state says localhost:9893_solr but ZooKeeper says localhost:9893_solr
which is confusing because there is no conflict.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]