[
https://issues.apache.org/jira/browse/SOLR-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834660#comment-13834660
]
Noble Paul commented on SOLR-5510:
----------------------------------
Ideally would like people to use collection admin commands to achieve this.
# call DELETEREPLICA and remove a node that died
# do a core create with appropriate collection/shard params or the upcoming
addNode api
However , we should not break an existing functionality. My patch should fix
this
> genericCoreNodeNames="${genericCoreNodeNames:false}" and old style solr.xml
> fails to create collection
> ------------------------------------------------------------------------------------------------------
>
> Key: SOLR-5510
> URL: https://issues.apache.org/jira/browse/SOLR-5510
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.6
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Minor
> Attachments: SOLR-5510.patch
>
>
> See this for some more details
> https://gist.github.com/serba/1fe113e78ae7e01a4f58
> This is a regression caused by SOLR-5311
> There are two reasons why a core does not have a reference in clusterstate
> # It is starting up for the first time (core creation)
> # Somebody invoked a DELETEREPLICA when the node itself was down
> we neded to differentiate these two because for 1) the registration should
> succeed and for #2 the registration should fail
> The only way to do that was to check for the presence of the attribute
> coreNodeName in the core.properties. In case #1 it would be absent and in
> case#2 it would be present
> but when genericCoreNodeNames="${genericCoreNodeNames:false}"
> ZkController#getCoreNodeName(getCoreNodeName) behaves similarly for both the
> cases and hence the failure
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
