[
https://issues.apache.org/jira/browse/SOLR-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter updated SOLR-6086:
---------------------------------
Attachment: SOLR-6086-temp.patch
Here's a patch I cooked up for this issue (against 6.3.0) ... it's not ready to
commit and needs a test, but does resolve my issue.
> Replica active during Warming
> -----------------------------
>
> Key: SOLR-6086
> URL: https://issues.apache.org/jira/browse/SOLR-6086
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.6.1, 4.8.1
> Reporter: Ludovic Boutros
> Assignee: Shalin Shekhar Mangar
> Labels: difficulty-medium, impact-medium
> Attachments: SOLR-6086.patch, SOLR-6086.patch, SOLR-6086-temp.patch
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> At least with Solr 4.6.1, replica are considered as active during the warming
> process.
> This means that if you restart a replica or create a new one, queries will
> be send to this replica and the query will hang until the end of the warming
> process (If cold searchers are not used).
> You cannot add or restart a node silently anymore.
> I think that the fact that the replica is active is not a bad thing.
> But, the HttpShardHandler and the CloudSolrServer class should take the
> warming process in account.
> Currently, I have developped a new very simple component which check that a
> searcher is registered.
> I am also developping custom HttpShardHandler and CloudSolrServer classes
> which will check the warming process in addition to the ACTIVE status in the
> cluster state.
> This seems to be more a workaround than a solution but that's all I can do in
> this version.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
