[
https://issues.apache.org/jira/browse/SOLR-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Blum updated SOLR-8722:
-----------------------------
Description:
We're doing an unnecessary ZkStateReader forced refresh on all Overseer
operations. This isn't necessary because ZkStateReader keeps itself up to date.
According to [~shalinmangar]'s analysis, we just need to put a wait loop at the
end of addReplica to observe the state change.
was:
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.
> Don't force a full ZkStateReader refresh on every Overseer operation
> --------------------------------------------------------------------
>
> Key: SOLR-8722
> URL: https://issues.apache.org/jira/browse/SOLR-8722
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 5.4.1
> Reporter: Scott Blum
> Assignee: Mark Miller
> Labels: patch, performance, solrcloud, startup
>
> We're doing an unnecessary ZkStateReader forced refresh on all Overseer
> operations. This isn't necessary because ZkStateReader keeps itself up to
> date.
> According to [~shalinmangar]'s analysis, we just need to put a wait loop at
> the end of addReplica to observe the state change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
