coreNodeName is the name of the znode that contains the data for the replica, including the replica’s name. So the znode core_node3 contains a property “core” with a value of catalogue_shard1_replca_n1
I’ve always found this a bit confusing, but that’s been true since very early days. Note that coreNodeName is invariant, whereas the core’s name can change. So for a replica to find it’s associated znode to know its role, an invariant is much better, thus it’s stored in core.properties. The only real changes from 6x is that the coreNodeName is now required in core.properties, so you noticed it. I’d strongly recommend you do not try to change this behavior. Best, Erick > On Mar 20, 2020, at 1:35 AM, vishal patel <vishalpatel200...@outlook.com> > wrote: > > I am upgrading Solr 6.1 to 8.3. I am creating collection using below API > http://10.31.32.29:8983/solr/admin/collections?_=1578288589068&action=CREATE&autoAddReplicas=false&collection.configName=catalogue&maxShardsPerNode=2&name=catalogue&numShards=2&replicationFactor=1&router.name=compositeId&wt=json&createNodeSet=10.31.32.29:8983_solr,15.21.12.21:8983_solr&createNodeSet.shuffle=false&property.name=catalogue > > My solr\catalogue_shard1_replica_n1\core.properties below: > > numShards=2 > collection.configName=catalogue > name=catalogue > replicaType=NRT > shard=shard1 > collection=catalogue > coreNodeName=core_node3 > > > I found out core name as catalogue_shard1_replica_n1 When I saw in Admin > panel. Why core name is mismatch in core property and admin panel. > After I got same name when rename API call : > 10.31.32.29:8983/solr/admin/cores?action=RENAME&core=catalogue_shard1_replica_n1&other=catalogue > > Actually I want to do same name of core and collection. Can I do at the time > of collection creation? > > Sent from Outlook<http://aka.ms/weboutlook>
