Thanks Amrit , Actually we have huge amount of data so that's why thinking to index data into particular shard accept it's looks difficult but need to achieve the performance using document routing for huge data.
With configuration of 4 shard and 4 replica is it better to distribute the one project data in multiple shard or in one shard which one is feasible using document routing because needs the best performance while insertion & retrieval of document. And there would be the multiple projects of client which has huge amount of data. I also taken the reading with 4 shard and 4 replica where without routing data are distribute among all 4 shard and with routing its distributes in 1 shard because of used 1 bit of shard key like projectId/1!DocumentId.my reading looks as below. 1:inserting data in 4 shard without document routing time taken ( in millisecond) =325108 Inserting data in 1 shard with document routing time time taken ( in millisecond) =251835 2: retrieving data from 4 shard without document routing time taken( in millisecond) = 234242 And retrieving data from 1 shard with document routing time taken ( in millisecond)= 94562 As per above reading getting performance in local while data in 1 shard but in production there will be huge data so is it need to distribute in 2 shard or in 1 shard which one is feasible for achieve better performance. Regards, Ketan -----Original Message----- From: Amrit Sarkar [mailto:sarkaramr...@gmail.com] Sent: Monday, November 13, 2017 8:52 PM To: solr-user@lucene.apache.org Subject: Re: How to routing document for send to particular shard range Surely someone else can chim in; but when you say: "so regarding to it we need to index the particular > client data into particular shard so if its manageable than we will > improve the performance as we need" You can / should create different collections for different client data, so that you can for surely improve performance as per need. There are multiple configurations which drives indexing and querying capabilities and incorporating everything in single collection will hinder that flexibility. Also if you need to add new client in future, you don't need to think about sharding again, add new collection and tweak its configuration as per need. Still if you need to use compositeKey to acheive your use-case, I am not sure how to do that honestly. Since shards are predefined when collection will be created. You cannot add more shards and such. You can only split a shard, which will divide the index and hence the hash range. I will strongly recommend you to reconsider your SolrCloud design technique for your use-case. Amrit Sarkar Search Engineer Lucidworks, Inc. 415-589-9269 www.lucidworks.com Twitter http://twitter.com/lucidworks LinkedIn: https://www.linkedin.com/in/sarkaramrit2 Medium: https://medium.com/@sarkaramrit2 On Mon, Nov 13, 2017 at 7:31 PM, Ketan Thanki <ktha...@asite.com> wrote: > > Thanks Amrit, > > My requirement to achieve best performance while using document > routing facility in solr so regarding to it we need to index the > particular client data into particular shard so if its manageable > than we will improve the performance as we need. > > Please do needful. > > > Regards, > > > -----Original Message----- > From: Amrit Sarkar [mailto:sarkaramr...@gmail.com] > Sent: Friday, November 10, 2017 5:34 PM > To: solr-user@lucene.apache.org > Subject: Re: How to routing document for send to particular shard > range > > Ketan, > > here I have also created new field 'core' which value is any shard > where I > > need to send documents and on retrieval use '_route_' parameter > > with mentioning the particular shard. But issue facing still my > > clusterstate.json showing the "router":{"name":"compositeId"} is it > > means my settings not impacted? or its default. > > > Only answering this query, as Erick has already mentioned in the above > comment. You need to RECREATE the collection passinfg the > "route.field" in the "create collection" api parameters as > "route.field" is collection-specific property maintained at zookeeper > (state.json / clusterstate.json). > > https://lucene.apache.org/solr/guide/6_6/collections- > api.html#CollectionsAPI-create > > I highly recommend not to alter core.properties manually when dealing > with SolrCloud and instead relying on SolrCloud APIs to make necessary change. > > Amrit Sarkar > Search Engineer > Lucidworks, Inc. > 415-589-9269 > www.lucidworks.com > Twitter http://twitter.com/lucidworks > LinkedIn: https://www.linkedin.com/in/sarkaramrit2 > Medium: https://medium.com/@sarkaramrit2 > > On Fri, Nov 10, 2017 at 5:23 PM, Ketan Thanki <ktha...@asite.com> wrote: > > > Hi Erik, > > > > My requirement to index the documents of particular organization to > > specific shard. Also I have made changes in core.properties as > > menions below. > > > > Model Collection: > > name=model > > shard=shard1 > > collection=model > > router.name=implicit > > router.field=core > > shards=shard1,shard2 > > > > Workset Collection: > > name=workset > > shard=shard1 > > collection=workset > > router.name=implicit > > router.field=core > > shards=shard1,shard2 > > > > here I have also created new field 'core' which value is any shard > > where I need to send documents and on retrieval use '_route_' > > parameter with mentioning the particular shard. But issue facing > > still my clusterstate.json showing the > > "router":{"name":"compositeId"} is it means my settings not impacted? or > > its default. > > > > Please do needful. > > > > Regards, > > > > -----Original Message----- > > From: Erick Erickson [mailto:erickerick...@gmail.com] > > Sent: Friday, November 10, 2017 12:06 PM > > To: solr-user > > Subject: Re: How to routing document for send to particular shard > > range > > > > You cannot just make configuration changes, whether you use implicit > > or compositeId is defined when you _create_ the collection and > > cannot be changed later. > > > > You need to create a new collection and specify router.name=implicit > > when you create it. Then you can route documents as you desire. > > > > I would caution against this though. If you use implicit routing > > _you_ have to insure balancing. For instance, you could have > > 10,000,000 documents for "Org1" and 15 for "Org2", resulting in > > hugely unbalanced > shards. > > > > Implicit routing is particularly useful for time-series indexing, > > where you, say, index a day's worth of documents to each shard. It > > may be appropriate in your case, but so far you haven't told us > > _why_ you think routing docs to particular shards is desirable. > > > > Best, > > Erick > > > > On Thu, Nov 9, 2017 at 10:27 PM, Ketan Thanki <ktha...@asite.com> wrote: > > > Thanks Amrit, > > > > > > For suggesting me the approach. > > > > > > I have got some understanding regarding to it and i need to > > > implement > > implicit routing for specific shard based. I have try by make > > changes on core.properties. but it can't work So can you please let > > me for the configuration changes needed. Is it need to create extra > > field for document to rout? > > > > > > I have below configuration Collection created manually: > > > 1: Workset with 4 shard and 4 replica > > > 2: Model with 4 shard and 4 replica > > > > > > > > > For e.g Core.properties for 1 shard : > > > Workset Colection: > > > name=workset > > > shard=shard1 > > > collection=workset > > > > > > Model Collection: > > > name=model > > > shard=shard1 > > > collection=model > > > > > > > > > So can u please let me the changes needed in configuration for the > > implicit routing. > > > > > > Please do needful. > > > > > > Regards, > > > > > > > > > -----Original Message----- > > > From: Amrit Sarkar [mailto:sarkaramr...@gmail.com] > > > Sent: Wednesday, November 08, 2017 12:36 PM > > > To: solr-user@lucene.apache.org > > > Subject: Re: How to routing document for send to particular shard > > > range > > > > > > Ketan, > > > > > > If you know defined indexing architecture; isn't it better to use > > "implicit" router by writing logic on your own end. > > > > > > If the document is of "Org1", send the document with extra param* > > > "_route_:shard1"* and likewise. > > > > > > Snippet from official doc: > > > https://lucene.apache.org/solr/guide/6_6/shards-and-indexing-data- > > > in -s > > > olrcloud.html#ShardsandIndexingDatainSolrCloud-DocumentRouting > > > : > > > > > > If you created the collection and defined the "implicit" router at > > > the time > > >> of creation, you can additionally define a router.field parameter > > >> to use a field from each document to identify a shard where the > > >> document belongs. If the field specified is missing in the > > >> document, however, the document will be rejected. You could also > > >> use the _route_ parameter to name a specific shard. > > > > > > > > > > > > Amrit Sarkar > > > Search Engineer > > > Lucidworks, Inc. > > > 415-589-9269 > > > www.lucidworks.com > > > Twitter http://twitter.com/lucidworks > > > LinkedIn: https://www.linkedin.com/in/sarkaramrit2 > > > Medium: https://medium.com/@sarkaramrit2 > > > > > > On Wed, Nov 8, 2017 at 11:15 AM, Ketan Thanki <ktha...@asite.com> > wrote: > > > > > >> Hi, > > >> > > >> I have requirement now quite different as I need to set routing > > >> key hash for document which confirm it to send to particular > > >> shard as its > > range. > > >> > > >> I have solrcloud configuration with 4 shard & 4 replica with > > >> below shard range. > > >> shard1: 80000000-bfffffff > > >> shard2: c0000000-ffffffff > > >> shard3: 0-3fffffff > > >> shard4: 40000000-7fffffff > > >> > > >> e.g: below show the project works in organization which is my > > >> routing > > key. > > >> Org1= works for project1,project2 Org2=works for project3 > > >> Org3=works for project4 > > >> Org4=project5 > > >> > > >> So as mentions above I want to index org1 to shard1,org2 to > > >> shard2,org3 to > > >> shard3,org4 to shard4 meanwhile send it to particular shard. > > >> How could I manage compositeId routing to do this. > > >> > > >> Regards, > > >> Ketan. > > >> Please cast a vote for Asite in the 2017 Construction Computing > Awards: > > >> Click here to > > >> Vote<http://caddealer.com/concompawards/index.php?page= > > >> cca2017vote> > > >> > > >> [CC Award Winners!] > > >> > > >> > > >
