bq: Only thing which we can achieve is , documents will be routed
based on the hash values of the field values.
Then you have created your collection with compositeID routing or have
some other misconfiguration. You _must_
create your collection with "router.name=implicit".
Rather than _tell_ us
Hi Ketan,
I believe you need multiple shard looking the count 800M. How much will be
the index size? Assume it comes out to 400G and assume your VM/machines
has 64GB and practically you want to fit your index into memory for each
shard... With that I would create 10shards on 10 machines (40 GB
Hi Ketan,
I also tried various ways to route documents to different shards based on
some routing key value. eg: status: active,inactive and terminated should
go to 3 different shards. I tried creating implicit as well as composite id
routers. I could not route the documents to the shard I want. O
Hi,
Can someone please let me for my below mentions use-case.
Regards,
Ketan
-Original Message-
From: Ketan Thanki
Sent: Wednesday, November 15, 2017 3:42 PM
To: 'solr-user@lucene.apache.org'
Subject: RE: How to routing document for send to particular shard range
Thanks Eri
ject: Re: How to routing document for send to particular shard range
These numbers aren't very useful. inserting how much data? Querying how much
data? What kinds of queries? Are you indexing in batches or one document at a
time? Are you using SolrJ and CloudSolrClient?
94 seconds to
> 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, N
ilto: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
> 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 clust
,
-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
...@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 '_
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=mo
: 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
;
> -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 defi
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 docum
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/shard
15 matches
Mail list logo
