GC_TUNE setting from solr.in.sh is not applied

2020-02-11 Thread Steffen Moldenhauer
Hi all, I installed Solr 8.4.1 (first time on a linux sub-system for testing purposes only) and for whatever reason the default GC settings prevented the server from running. So I tried to change the setting with a GC_TUNE in solr.in.sh But it got not applied to the start up. So I looked at the

RE: Asynchronous Calls to Backup/Restore Collections ignoring errors

2019-02-06 Thread Steffen Moldenhauer
electChannelEndPoint.jav > a:93) > >at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProdu > ceConsume(ExecuteProduceConsume.java:303) > >at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceCons > ume(ExecuteProduceConsume.java:148) > >at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecutePr > oduceConsume.java:136) > >at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.ja > va:671) > >at > org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.ja > va:589) > >at java.lang.Thread.run(Thread.java:748) > > 500 > > > > > > But we cannot use the sync call because we are running in a timout even if > we increase the socket timeout of the client. > > And we cannot use the async because it does not report errors. > > > > Is this a known bug? Any ideas for a workaround? > > > > Kind regards > > Steffen Moldenhauer > >

Asynchronous Calls to Backup/Restore Collections ignoring errors

2019-01-31 Thread Steffen Moldenhauer
oes not report errors. Is this a known bug? Any ideas for a workaround? Kind regards Steffen Moldenhauer