lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nimesh Aghera <nagh...@asite.com>
Subject RE: Implicit routing changes to Composite while re-deploy changes and make Upconfig command
Date Wed, 13 Dec 2017 11:06:31 GMT


Hi Erik,



Thanks for the reply.



Currently using solr cloud 6.1.0 and below is the solr admin UI which shows that routing changes
after make upconfig command



Below image are before make  re-upconfig where all data are indexed into particular shard.



AMS_Config:

[cid:image001.png@01D37430.873F2130]





Model Collection:  Created collection using Collection API and also data index into particular
shard



[cid:image002.png@01D37430.873F2130]



But after that I have make schema changes (Not Mandatory) and do upconfig as mention in previsou
mail and start the solr instance its  shows my model collection as below and also it index
data across all shards

[cid:image003.png@01D37430.873F2130]







Its causes issues that if any how its required to make upconfig than it change the routing
from implicit to compositeId.



Please do needful.



Regards,

Nimesh Aghera





-----Original Message-----
From: Erick Erickson [mailto:erickerickson@gmail.com]
Sent: Tuesday, December 12, 2017 9:29 PM
To: solr-user
Subject: Re: Implicit routing changes to Composite while re-deploy changes and make Upconfig
command



bq: It will changes the router value implicit to compositeId



What evidence do you have of that? This better not happen. The routing scheme is part of the
collection creation command and is stored in ZooKeeper in the collection's znode, it has nothing
to do with the configset so updating the configs shouldn't change that at all.



Best,

Erick



On Tue, Dec 12, 2017 at 1:15 AM, Nimesh Aghera <naghera@asite.com<mailto:naghera@asite.com>>
wrote:

> Hello,

>

> I have implemented implicit routing with below configuration.

> Created one default collection manually 'AMS_Config' which contains configurations files
 schema,solrconfig etc.

>

> Using 'AMS_Config' I have created 2 collections model,workset respectively with below
command which created 2 shard for each collection containing 2 node for each shard where nodes
are each solr instance where collection created.

>

> Command:

> /admin/collections?action=CREATE&name=model&replicationFactor=2&router

> .name=implicit&router.field=dr&shards=shard1,shard2&maxShardsPerNode=2

> &collection.configName=AMS_Config

>

> Collection Detail:

> Model = Shard1,Shard2

> Shard1 = node1,node2[leader]

> Shard2 =node1[leader],node2

>

> Configuration in admin UI on solr for model collection:

> Shard count:2

> configName:AMS_Config

> replicationFactor:2

> maxShardsPerNode:2

> router:implicit

> autoAddReplicas:false

>

> after this I have index document to particular shard using set value

> (router.field) dr = shard1

>

> Issue:  After indexing the document made changes in schema files and

> redeploy using below command  for set latest configs zkcli.bat -cmd

> upconfig -confdir ../../solr/AMS_Config/conf -confname AMS_Config -z

> <zk Ips>

>

> It will changes the router value implicit to compositeId and now my document are index
across all shard so why this should happens.How to avoid this.

>

> Please do the needful.

>

> Regards,

> Nimesh Aghera

>

> [CC Award Winners!]

>
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message