[
https://issues.apache.org/jira/browse/SOLR-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-5702:
------------------------------
Priority: Minor (was: Major)
Fix Version/s: 4.7
5.0
Assignee: Mark Miller
> info-log collection.configName in ZkStateReader.readConfigName
> --------------------------------------------------------------
>
> Key: SOLR-5702
> URL: https://issues.apache.org/jira/browse/SOLR-5702
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.6.1
> Reporter: Christine Poerschke
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 5.0, 4.7
>
>
> The scenario we had was that a solr instance for an existing collection did
> mysteriously not use the -Dcollection.configName=<new value> specified
> config. This it turned out was rightly so because zookeeper already had a
> configName=<old value> for the already existing collection.
> org.apache.solr.cloud.ZkCLI linkconfig needs to be run to update the existing
> value if required.
> Solr info-logging the configName it uses would help developers in this
> scenario.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
