You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2010/03/18 18:38:27 UTC
[jira] Created: (ZOOKEEPER-714) snapshotting doesn't handle runtime
exceptions (like out of memory) well
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
Fix For: 3.3.1
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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-714) snapshotting doesn't handle runtime
exceptions (like out of memory) well
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-714:
-----------------------------------
Fix Version/s: 3.4.0
> 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
> Fix For: 3.3.1, 3.4.0
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.