[
https://issues.apache.org/jira/browse/SOLR-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070379#comment-14070379
]
Ramkumar Aiyengar commented on SOLR-6261:
-----------------------------------------
Alternative approach using an executor, just a sketch at this point (still
fails a few tests). It has an `instanceof` which is a bit ugly, but any other
method to maintain existing behaviour when needed can be used, this was just
the simplest.. Once we are settled on the approach, we can hunt down other
stuff using the event thread..
https://github.com/apache/lucene-solr/pull/66/files
(would be nice if commits to a pull showed up here..)
> Run checkIfIamLeader in a separate thread
> -----------------------------------------
>
> Key: SOLR-6261
> URL: https://issues.apache.org/jira/browse/SOLR-6261
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.9
> Reporter: Ramkumar Aiyengar
> Assignee: Mark Miller
> Priority: Minor
>
> Currently checking for leadership (due to the leader's ephemeral node going
> away) happens in ZK's event thread. If there are many cores and all of them
> are due leadership, then they would have to serially go through the two-way
> sync and leadership takeover.
> For tens of cores, this could mean 30-40s without leadership before the last
> in the list even gets to start the leadership process. If the leadership
> process happens in a separate thread, then the cores could all take over in
> parallel.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
