[
https://issues.apache.org/jira/browse/SOLR-8696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-8696:
------------------------------
Attachment: SOLR-8696.patch
New patch. Fixes the same overseer situation on zk reconnect (I've seen the
logging that shows this problem is really and kind of ugly there too) and
removes the forced refresh change.
> 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
> Attachments: 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: [email protected]
For additional commands, e-mail: [email protected]
