On 8/16/2024 15:05, mtn search wrote:
oom_solr.sh is provided by Solr to kill the solr process on OOM and log
this event. Is it a common practice to then also create supporting
functionality to automatically restart solr after the kill?
IMHO, in general, it is a bad idea to automatically
attached to the new pod.
On Wed, Aug 21, 2024 at 10:07 AM wrote:
> On Fri, Aug 16, 2024 at 09:05:58PM +, mtn search wrote:
> > oom_solr.sh is provided by Solr to kill the solr process on OOM and log
> > this event. Is it a common practice to then also create supporting
>
On Fri, Aug 16, 2024 at 09:05:58PM +, mtn search wrote:
> oom_solr.sh is provided by Solr to kill the solr process on OOM and log
> this event. Is it a common practice to then also create supporting
> functionality to automatically restart solr after the kill?
It makes sense to me,
search
Sent: Friday, August 16, 2024 4:05 PM
To: users@solr.apache.org
Subject: oom_solr.sh
Hello, oom_solr. sh is provided by Solr to kill the solr process on OOM and log
this event. Is it a common practice to then also create supporting
functionality to automatically restart solr after the
Hello,
oom_solr.sh is provided by Solr to kill the solr process on OOM and log
this event. Is it a common practice to then also create supporting
functionality to automatically restart solr after the kill?
- On *nix systems, we recommend that Solr be run with the "OOM killer
script&
