[
https://issues.apache.org/jira/browse/SOLR-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yago Riveiro RodrÃguez closed SOLR-4292.
----------------------------------------
Resolution: Not A Problem
> After upload and link config collection, the collection in solrcloud not load
> the new config
> --------------------------------------------------------------------------------------------
>
> Key: SOLR-4292
> URL: https://issues.apache.org/jira/browse/SOLR-4292
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 4.0
> Environment: CentOS release 6.3 (Final)
> Linux app-solr-00 2.6.32-279.14.1.el6.x86_64 #1 SMP Tue Nov 6 23:43:09 UTC
> 2012 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Yago Riveiro RodrÃguez
>
> I'm trying to change the settings for a specific collection, which is empty,
> with a new config.
> The collection has 2 shards, and the zookeeper is a cluster of 3 servers.
> I used the zookeeper to upload the configuration and link it with the
> collection. After this, I reloaded the collection in both nodes (replica and
> leader) but when I try to see the STATUS of collection's core
> (/solr/admin/cores?action=STATUS&wt=json&indent=true) I get this error:
>
> "ST-4A46DF1563_0812":"org.apache.solr.common.cloud.ZooKeeperException:org.apache.solr.common.cloud.ZooKeeperException:
> Specified config does not exist in
> ZooKeeper:statisticsBucket-aggregation-revision-1"
> The clusterstate.json shows that the ST-4A46DF1563_0812 has loaded the
> configname: {"configName":"statisticsBucket-aggregation-revision-1"}
> If the zookeeper has the new config loaded and I linked the config to the
> collection, why the status of core says that the configuration is missing?
> /Yago
--
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: [email protected]
For additional commands, e-mail: [email protected]
