[
https://issues.apache.org/jira/browse/SOLR-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893662#comment-13893662
]
ASF subversion and git services commented on SOLR-5702:
-------------------------------------------------------
Commit 1565399 from [~markrmil...@gmail.com] in branch 'dev/trunk'
[ https://svn.apache.org/r1565399 ]
SOLR-5702: Log config name found for collection at info level.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
