zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enrico Olivelli (Jira)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-714) snapshotting doesn't handle runtime exceptions (like out of memory) well
Date Fri, 06 Sep 2019 15:45:06 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Enrico Olivelli updated ZOOKEEPER-714:
--------------------------------------
    Fix Version/s:     (was: 3.5.6)

> snapshotting doesn't handle runtime exceptions (like out of memory) well
> ------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-714
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-714
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.2.2
>            Reporter: Patrick Hunt
>            Priority: Major
>             Fix For: 3.6.0, 3.5.7
>
>
> If an out of memory occurs during snapshotting we recover from the error, however we
should be more explict about the problem. 
> Currently we log a warning, really we should log a FATAL and exit. This would force the
server to restart (supervisor) and make it very clear to the user there is a problem. In some
cases users don't notice the OOM exception (we have trouble noticing it sometimes ourselves)
as it doesn't stand out on the logs. Exiting would be more explicit. However since we'd like
to remove sysexits due to container issues it's not clear what we should do here in addition
to making this FATAL.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message