Core name mismatch in Solr admin panel 8.3

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Core name mismatch in Solr admin panel 8.3

vishal patel-2
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>
Reply | Threaded
Open this post in threaded view
|

Re: Core name mismatch in Solr admin panel 8.3

Erick Erickson
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 <[hidden email]> 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>

Reply | Threaded
Open this post in threaded view
|

Re: Core name mismatch in Solr admin panel 8.3

vishal patel-2
I want to change the core name not coreNodeName. Actually I want to check the status of core using http://10.31.32.29:8983/solr/admin/cores?action=STATUS&core=<http://10.38.33.28:8983/solr/admin/cores?action=STATUS&core=reports_shard1_replica_n1>catalogue<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>.
It is good for us if core name and collection name will same. For this I will give the core name &property.name=catalogue<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> at the time of collection creation. It updated in core.property as name=catalogue<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>. But when I hit the URL http://10.31.32.29:8983/solr/admin/cores?action=STATUS&core=<http://10.38.33.28:8983/solr/admin/cores?action=STATUS&core=reports_shard1_replica_n1>catalogue<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> i can not get the result.

After I renamed using 10.31.32.29:8983/solr/admin/cores?action=RENAME&core=catalogue_shard1_replica_n1&other=catalogue  and got proper result.
[After rename there is no any changes in core.property but in admin panel I can see core name as catalogue].

Regards,
Vishal


Sent from Outlook<http://aka.ms/weboutlook>
________________________________
From: Erick Erickson <[hidden email]>
Sent: Friday, March 20, 2020 6:12 PM
To: [hidden email] <[hidden email]>
Subject: Re: Core name mismatch in Solr admin panel 8.3

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 <[hidden email]> 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>