Query-heavy (100 queries per sec)
scenario?
Thanks & Regards,
Bhaumik Joshi
From: Shawn Heisey
Sent: Tuesday, April 12, 2016 7:37 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr Sharding Strategy
On 4/11/2016 6:31 AM, Bhaumik Joshi wrote:
>
On 4/11/2016 6:31 AM, Bhaumik Joshi wrote:
> We are using solr 5.2.0 and we have Index-heavy (100 index updates per
> sec) and Query-heavy (100 queries per sec) scenario.
>
> *Index stats: *10 million documents and 16 GB index size
>
>
>
> Which sharding strategy is best suited in above scenario?
user@lucene.apache.org
Subject: Re: Solr Sharding Strategy
On Tue, 2016-04-12 at 05:57 +, Bhaumik Joshi wrote:
> //Insert Document
> UpdateResponse resp = cloudServer.add(doc, 1000);
>
Don't insert documents one at a time, if it can be avoided:
https://lucidworks.com/blog/2015/10/05/re
On Tue, 2016-04-12 at 05:57 +, Bhaumik Joshi wrote:
> //Insert Document
> UpdateResponse resp = cloudServer.add(doc, 1000);
>
Don't insert documents one at a time, if it can be avoided:
https://lucidworks.com/blog/2015/10/05/really-batch-updates-solr-2/
Try pausing the indexing fully when y
oshi
From: Daniel Collins
Sent: Monday, April 11, 2016 8:12 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr Sharding Strategy
I'd also ask about your indexing times, what QTime do you see for indexing
(in both scenarios), and what commit times are you using (which Tok
I'd also ask about your indexing times, what QTime do you see for indexing
(in both scenarios), and what commit times are you using (which Toke
already asked).
Not entirely sure how to read your table, but looking at the indexing side
of things, with 2 shards, there is inherently more work to do,
On Mon, 2016-04-11 at 11:23 +, Bhaumik Joshi wrote:
> We are using solr 5.2.0 and we have Index-heavy (100 index updates per
> sec) and Query-heavy (100 queries per sec) scenario.
> Index stats: 10 million documents and 16 GB index size
> Which sharding strategy is best suited in above scenar