You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Timothy Potter (JIRA)" <ji...@apache.org> on 2015/05/28 18:41:18 UTC

[jira] [Resolved] (SOLR-7503) Recovery after ZK session expiration happens in a single thread for all cores in a node

     [ https://issues.apache.org/jira/browse/SOLR-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Potter resolved SOLR-7503.
----------------------------------
    Resolution: Fixed

> Recovery after ZK session expiration happens in a single thread for all cores in a node
> ---------------------------------------------------------------------------------------
>
>                 Key: SOLR-7503
>                 URL: https://issues.apache.org/jira/browse/SOLR-7503
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 5.1
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Timothy Potter
>              Labels: impact-high
>             Fix For: Trunk, 5.2
>
>         Attachments: SOLR-7503.patch
>
>
> Currently cores are registered in parallel in an executor. However, when there's a ZK expiration, the recovery, which also happens in the register call, happens in a single thread:
> https://github.com/apache/lucene-solr/blob/trunk/solr/core/src/java/org/apache/solr/cloud/ZkController.java#L300
> We should make these happen in parallel as well so that recovery after ZK expiration doesn't take forever.
> Thanks to [~mewmewball] for catching this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org