[
https://issues.apache.org/jira/browse/SOLR-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-5071.
----------------------------------
Resolution: Not A Problem
Daniel pretty well nailed it. Changing a local solr.xml and having ZooKeeper
pick it up somehow is unsupported.
A minor correction though. The current form of solr.xml _will_ be supported in
Solr 4.4 and all of Solr 4.x, even though it's deprecated. As of Solr 5.0
(current trunk) that support will be removed.
> Solrcloud change core to another shard issue
> --------------------------------------------
>
> Key: SOLR-5071
> URL: https://issues.apache.org/jira/browse/SOLR-5071
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Illu Y Ying
> Attachments: 2013-7-24 11-55-45.png
>
>
> I have a solrcloud cluster with one collection and two shards.
> One core is a replica for shard1, I stop it and change its solr.xml like this:
> <core name="collection1" instanceDir="collection1" shard="shard2"/>
> So this core should be a shard2 replica, Then I restart it, open cloud graph
> page(see attachment), you can see this core as a down replica still in shard1
> and also as a active replica in shard2.
> There is doubt about one core status in two shards.
> In this one core has two status scenario I suggest that if we could remove
> the down replica information of other shard in clusterStatus.json.
> I remember when core is changing to active status, it will send overseer an
> active status message, so add this logic to overseer change core to active
> status part.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
