Got it but unless you know what caused OOM you can run into this again.
Restart may not help really.
You should try to find out from gc logs if it was sudden increase which
caused OOM (some culprit query or heavy ingestion) or it was over the
period of time (due to cache util..).
Based on that yo
Thanks Furkan.
Hi Susheel - our Solr was running so long until we experienced Solr went system
out of memory. we already increased the virtual memory and so far so good. we
just want an automated restart to refresh Solr, just another proactive
initiative.
Best Regards,
Jeck
> On 3 Jul 2017, a
I am curios why you need to restart solr every week. Our Prod solr
instance (6.0) has been running Since Nov,16 with no restart
On Sun, Jul 2, 2017 at 12:55 PM, Furkan KAMACI
wrote:
> Hi Jeck,
>
> Here is the documentation about how you can run Solr as service:
> https://lucene.apache.org/solr/
Hi Jeck,
Here is the documentation about how you can run Solr as service:
https://lucene.apache.org/solr/guide/6_6/taking-solr-to-production.html
However, as far as I see you use Windows as operating system. There is
currently an open issue for creating scripts to run as a Windows Service:
https:
Hi,
Anyone who successfully set this up? Thanks
Best Regards,
Jeck
> On 20 Jun 2017, at 7:10 PM, rojerick luna wrote:
>
> Hi,
>
> I'm trying to automate Solr restart every week.
>
> I created a stop.bat and updated the start.bat which I found on an article
> online. Using stop.bat and start
Hi,
I'm trying to automate Solr restart every week.
I created a stop.bat and updated the start.bat which I found on an article
online. Using stop.bat and start.bat is working fine. However when I created a
Task Scheduler (Windows Scheduler) and setup the frequency to stop and start
(using the
