Re: SOLR Cloud: 1500+ threads are in TIMED_WAITING status

Hi, Is there any solution found for this issue. We are using Solr 7.6 and sometimes we do see lot of QTP threads with the stack trace sun.misc.Unsafe.park(Native method) java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) java.util.concurrent.locks.AbstractQueuedSynchronizer$Co

Re: SOLR Cloud: 1500+ threads are in TIMED_WAITING status

Hi, Is there any network parameter that we need to fine tune? Is there any specific tweaking needed to deploy solr in virtual machines? We use VMware. Thanks. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: SOLR Cloud: 1500+ threads are in TIMED_WAITING status

Hi Emir, Just realised DBQ = Delete by Query, we are not using that, we are deleting documents using the document id / unique id. Thanks, Mohandoss. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: SOLR Cloud: 1500+ threads are in TIMED_WAITING status

Hi Mohandoss, I would check to see if thread increase is correlated to DBQ since it does not play well with concurrent indexing: http://www.od-bits.com/2018/03/dbq-or-delete-by-query.html HTH, Emir -- Monitoring - Log Management - Ale

Re: SOLR Cloud: 1500+ threads are in TIMED_WAITING status

Hi Emir, We do fire delete queries but that is very very minimal. Thanks! Mohandoss -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: SOLR Cloud: 1500+ threads are in TIMED_WAITING status

Hi, I’ve seen similar jump in thread number when DBQ was used. Do you delete documents while indexing? Emir -- Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > On 5 Apr 2018, at 07:56, Doss wrote: > > @wunder

Re: SOLR Cloud: 1500+ threads are in TIMED_WAITING status

@wunder Are you sending updates in batches? Are you doing a commit after every update? >> We want the system to be near real time, so we are not doing updates in >> batches and also we are not doing commit after every update. >> autoSoftCommit once in every minute, and autoCommit once in every

Re: SOLR Cloud: 1500+ threads are in TIMED_WAITING status

Are you sending updates in batches? Are you doing a commit after every update? You should use batches and you should not commit after every update. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Apr 4, 2018, at 8:01 PM, 苗海泉 wrote: > > A lot of col

Re: SOLR Cloud: 1500+ threads are in TIMED_WAITING status

A lot of collection time, we also found that there are a lot of time_wait thread, mainly committed submit thread and search thread, which led to the rapid decline in the speed of solr, the number of these threads up to more than 2,000. I didn't have a solution to this problem, but I found that relo