Re: Supporting multiple indexes in one collection

How many documents ? > The real difference was only a couple of ms? > > > Am 01.07.2020 um 07:34 schrieb Raji N : > > > > Had 2 indexes in 2 separate shards in one collection and had exact same > > data published with composite router with a prefix. Disabled all caches

Re: Supporting multiple indexes in one collection

same time ) were more in 2 indexes with 2 separate shards case. 90th percentile response time was also few ms better. Thanks, Raji On Tue, Jun 30, 2020 at 10:06 PM Jörn Franke wrote: > What did you test? Which queries? What were the exact results in terms of > time ? > > > Am 30.0

Supporting multiple indexes in one collection

. We saw the performance for the first case (placing an index explicitly on a shard ) is better. Has anyone done anything similar. Can you please share your experience. Thanks, Raji

Re: off-heap OOM

like it happens due to running out of threads. Rather suspecting it happens because there is no native memory?. Thanks, Raji On Fri, May 1, 2020 at 12:13 AM Mikhail Khludnev wrote: > > java.lang.OutOfMemoryError: unable to create new native thread > Usually mean code flaw, but there is

Re: off-heap OOM

0_211] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_211] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_211] Thanks, Raji On Thu, Apr 30, 2020 at 12:24 AM Mikhail Khludnev wrote:

Re: off-heap OOM

Thanks so much Jan. Will try your suggestions , yes we are also running solr inside docker. Thanks, Raji On Wed, Apr 29, 2020 at 1:46 PM Jan Høydahl wrote: > I have seen the same, but only in Docker. > I think it does not relate to Solr’s off-heap usage for filters and other > data s

Re: off-heap OOM

uild 25.211-b12, mixed mode) Thanks much for taking a look at it. Raji On Wed, Apr 29, 2020 at 10:04 AM Shawn Heisey wrote: > On 4/29/2020 2:07 AM, Raji N wrote: > > Has anyone encountered off-heap OOM. We are thinking of reducing heap > > further and increasing the h

Re: IdleTimeout setting in Jetty (Solr 7.7.1)

Try starting like this. bin/solr start -Dsolr.jetty.threads.idle.timeout=2000 -z localhost:2181 Hope this helps Raji On Sun, Apr 26, 2020 at 11:24 PM Kommu, Vinodh K. wrote: > Can someone shed some idea on below requirement? > > Thanks & Regards, > Vinodh > >

off-heap OOM

mit every 2 mins. Has anyone encountered off-heap OOM. We are thinking of reducing heap further and increasing the hardcommit interval . Any other suggestions? . Please share your thoughts. Thanks, Raji

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

(QueuedThreadPool.java:48) org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:717) java.lang.Thread.run(Thread.java:748) Thanks, Raji -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Solrcloud 7.6 OOM due to unable to create native threads

Hi Eric, What are you recommendations for SolrCloud DR strategy. Thanks, Raji On Sun, Mar 29, 2020 at 6:25 PM Erick Erickson wrote: > I don’t recommend CDCR at this point, I think there better approaches. > > The root problem is that CDCR uses tlog files as a queueing mechanism.

Re: Solrcloud 7.6 OOM due to unable to create native threads

hreadPoolExecutor.java:1134) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Thanks, Raji On Sun, Mar 29, 2020 at 5:18 AM Erick Erickson wrote: > What that error usually means is that there are a zi

Solrcloud 7.6 OOM due to unable to create native threads

r.run(ThreadPoolExecutor.java:624) [?:1.8.0_211] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_211] Thanks, Raji