Forest Soup created SOLR-7982:
---------------------------------
Summary: SolrCloud: There are duplicate coreNodeName in
core.properties in a same collection after the collection is created.
Key: SOLR-7982
URL: https://issues.apache.org/jira/browse/SOLR-7982
Project: Solr
Issue Type: Bug
Components: SolrCloud
Affects Versions: 4.7
Environment: linux redhat enterprise server 5.9 64bit
Reporter: Forest Soup
We have a 3 Zookeeper 5 solr server Solrcloud.
We created collection1 and collection2 with 80 shards respectively in the
cloud, replicateFactor is 2.
But after created, we found in a same collection, the coreNodeName has some
duplicate in core.properties in the core folder. For example:
[tanglin@solr64 home]$ ll collection1_shard13_replica2/core.properties
-rw-r--r-- 1 solr solr 173 Jul 29 11:52
collection1_shard13_replica2/core.properties
[tanglin@solr64 home]$ ll collection1_shard66_replica1/core.properties
-rw-r--r-- 1 solr solr 173 Jul 29 11:52
collection1_shard66_replica1/core.properties
[tanglin@solr64 home]$ cat collection1_shard66_replica1/core.properties
#Written by CorePropertiesLocator
#Wed Jul 29 11:52:54 UTC 2015
numShards=80
name=collection1_shard66_replica1
shard=shard66
collection=collection1
coreNodeName=core_node19
[tanglin@solr64 home]$ cat collection1_shard13_replica2/core.properties
#Written by CorePropertiesLocator
#Wed Jul 29 11:52:53 UTC 2015
numShards=80
name=collection1_shard13_replica2
shard=shard13
collection=collection1
coreNodeName=core_node19
[tanglin@solr64 home]$
The consequence of the issue is that the clusterstate.json in zookeeper is also
with wrong core_node#, and updating state of a core sometimes changed the state
of other core in other shard..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
