[
https://issues.apache.org/jira/browse/SOLR-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990917#comment-13990917
]
ASF subversion and git services commented on SOLR-5993:
-------------------------------------------------------
Commit 1592821 from [email protected] in branch 'dev/branches/lucene_solr_4_8'
[ https://svn.apache.org/r1592821 ]
Merge back several "low hanging" bug fixes into the 4.8 branch...
SOLR-6029: r1590867
SOLR-6030: r1591555
SOLR-6037: r1591800
SOLR-6023: r1592195
SOLR-5090: r1592591
SOLR-6039: r1592605
SOLR-5993: r1588415
SOLR-5904: r1587702
> 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
> Assignee: Shalin Shekhar Mangar
> Priority: Trivial
> Fix For: 4.9, 5.0
>
> Attachments: SOLR-5993.patch
>
>
> 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]
