[
https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172616#comment-15172616
]
ASF subversion and git services commented on SOLR-8696:
-------------------------------------------------------
Commit a9aec24236df61a3f1cfe533b64169fae84fc6f7 in lucene-solr's branch
refs/heads/master from [~markrmil...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=a9aec24 ]
SOLR-8696: Straighten out calls to
ZkStateReader#createClusterStateWatchersAndUpdate.
> Start the Overseer before actions that need the overseer on init and when
> reconnecting after zk expiration and improve init logic.
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-8696
> URL: https://issues.apache.org/jira/browse/SOLR-8696
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 5.4.1
> Reporter: Scott Blum
> Assignee: Mark Miller
> Labels: patch, performance, solrcloud, startup
> Fix For: master
>
> Attachments: SOLR-8696-followup.patch, SOLR-8696.patch,
> SOLR-8696.patch
>
>
> ZkController.publishAndWaitForDownStates() occurs before overseer election.
> That means if there is currently no overseer, there is ironically no one to
> actually service the down state changes it's waiting on. This particularly
> affects a single-node cluster such as you might run locally for development.
> Additionally, we're doing an unnecessary ZkStateReader forced refresh on all
> Overseer operations. This isn't necessary because ZkStateReader keeps itself
> up to date.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
