[
https://issues.apache.org/jira/browse/SOLR-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085282#comment-14085282
]
Ramkumar Aiyengar commented on SOLR-6261:
-----------------------------------------
Mark, I realized I missed a case, the session watcher doesn't use this
threadpool. In theory it should be fine as of now, as we already made it async
with SOLR-5615, but might be worth keeping it in sync and avoiding any future
code in {{ConnectionManager}} falling into the same trap. I have a patch and
running through tests which I can post when done, should I create a new issue
or put the patch here?
> Run ZK watch event callbacks in parallel to the event 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
> Fix For: 5.0, 4.10
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
