[
https://issues.apache.org/jira/browse/SOLR-16887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743255#comment-17743255
]
Shawn Heisey commented on SOLR-16887:
-------------------------------------
I am not changing heap dump options.
It looks like the container is not doing heap dumps by default... whatever
mechanism people are using to create heap dumps would most likely be unaffected
by this change.
> The new "Crash On Out Of Memory Error" capability breaks auto-restart on the
> docker container
> ---------------------------------------------------------------------------------------------
>
> Key: SOLR-16887
> URL: https://issues.apache.org/jira/browse/SOLR-16887
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Affects Versions: main (10.0), 9.2.0
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Major
> Attachments: SOLR-16887-1.patch, SOLR-16887-2.patch,
> SOLR-16887-3.patch, SOLR-16887.patch
>
>
> In SOLR-8803 I changed OOME handling from a shell script to Java's
> CrashOnOutOfMemoryError feature.
> It was revealed that this breaks automatic restarting of Solr inside the
> docker container.
> This issue will change OOME handling from CrashOnOutOfMemoryError to
> ExitOnOutOfMemoryError. With that option, the cause of the OOME is logged by
> Java to the console. There were two primary motivations behind changing the
> behavior in SOLR-8803: 1) Cross-platform OOME handling. 2) Always having
> the cause of any OOME available. This change will preserve both of those.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
