Re: Solr Collection Reload

2020-12-16 Thread Moulay Hicham
ok at that, perhaps there’s some > deadlock. > > But that said, a reload shouldn’t take more time > than a startup… > > Best, > Erick > > > On Dec 14, 2020, at 5:44 PM, Moulay Hicham wrote: > > > > Hi, > > > > I have an issue with the collect

Solr Collection Reload

2020-12-14 Thread Moulay Hicham
Hi, I have an issue with the collection reload API. The reload seems to be hanging. It's been in the running state for many days. Can you please suggest any documentation which explains the reload task under the hood steps? FYI. I am using solr 8.1 Thanks, Moulay

Collection reload issue

2020-12-12 Thread Moulay Hicham
Hi, I am using solr 8.1 I ran a collection reload operation: admin/collections?action=RELOAD&name=&async=1000'. when I checked on the task status, it shows that it's still running: admin/collections?action=REQUESTSTATUS&requestid=1000' It's been showing that this task is in running state for th

Re: Solr Collection reload task has been in running state for a very long time

2020-12-11 Thread Moulay Hicham
Hi, I will really appreciate if someone can help me with this. Thank you, Moulay On Thu, Dec 10, 2020, 8:28 AM Moulay Hicham wrote: > Hi, > > We have a solr cluster of 30 nodes with a Replication Factor =3. > Each index size is about 80GB. > Solr version is 8.1 > The cl

Solr Collection reload task has been in running state for a very long time

2020-12-10 Thread Moulay Hicham
Hi, We have a solr cluster of 30 nodes with a Replication Factor =3. Each index size is about 80GB. Solr version is 8.1 The cluster has high TPS both in read and write. We have recently made a schema change and uploaded it using ZKCLI script. Then we issue a collection reload async request: admin

Collection reload task is taking long time

2020-12-09 Thread Moulay Hicham
Hi, We have a solr cluster of 30 nodes with a Replication Factor =3. Each index size is about 80GB. Solr version is 8.1 The cluster has high TPS both in read and write. We have recently made a schema change and uploaded it using ZKCLI script. Then we issue a collection reload async request: admin

Re: TieredMergePolicyFactory question

2020-10-26 Thread Moulay Hicham
NOTE: after your last > expungeDeletes, deleted docs will accumulate over time until they reach a > plateau and > shouldn’t continue increasing after that. If you can _prove_ that > accumulating deleted > documents affects performance, institute a regular expungeDeletes. > Optimize, but

Re: TieredMergePolicyFactory question

2020-10-25 Thread Moulay Hicham
This is not a hard number, and in practice the percentage of you index > that consists > of deleted documents tends to be lower than this number, depending of > course > on your particular environment. > > Best, > Erick > > > On Oct 23, 2020, at 12:59 PM, Moulay Hic

Re: TieredMergePolicyFactory question

2020-10-23 Thread Moulay Hicham
eletes, that will rewrite all segments with > more than 10% deleted docs. As of Solr 7.5, these operations respect the 5G > limit. > > See: https://lucidworks.com/post/solr-and-optimizing-your-index-take-ii/ > > Best > Erick > > On Fri, Oct 23, 2020, 12:36 Moulay Hicham wr

TieredMergePolicyFactory question

2020-10-23 Thread Moulay Hicham
Hi, I am using solr 8.1 in production. We have about 30%-50% of deleted documents in some old segments that were merged a year ago. These segments size is about 5GB. I was wondering why these segments have a high % of deleted docs and found out that they are NOT being candidates for merging beca