You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2017/05/02 18:56:04 UTC
[jira] [Resolved] (SOLR-10316) Unloading a core can remove a ZK
SolrCore registration entry for the wrong SolrCore.
[ https://issues.apache.org/jira/browse/SOLR-10316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Miller resolved SOLR-10316.
--------------------------------
Resolution: Fixed
Fix Version/s: master (7.0)
6.6
> Unloading a core can remove a ZK SolrCore registration entry for the wrong SolrCore.
> ------------------------------------------------------------------------------------
>
> Key: SOLR-10316
> URL: https://issues.apache.org/jira/browse/SOLR-10316
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 6.6, master (7.0)
>
> Attachments: SOLR-10316.patch, SOLR-10316.patch
>
>
> We only use core node name and collection to match in ZK#unregister(core).
> This means if a registration was taken over (either via manual user interaction or auto add replicas), unloading a core can remove a ZK entry it should not.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org