zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flavio Junqueira (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-602) log all exceptions not caught by ZK threads
Date Sun, 17 May 2015 15:53:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547208#comment-14547208
] 

Flavio Junqueira commented on ZOOKEEPER-602:
--------------------------------------------

I'm not entirely sure we should be exiting in the case there is error that stops a critical
thread in a request processor. Why not stopping the instance and restart election for the
server rather than calling system.exit on the server?


> log all exceptions not caught by ZK threads
> -------------------------------------------
>
>                 Key: ZOOKEEPER-602
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-602
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client, server
>    Affects Versions: 3.2.1
>            Reporter: Patrick Hunt
>            Assignee: Rakesh R
>            Priority: Blocker
>             Fix For: 3.4.7, 3.5.0
>
>         Attachments: ZOOKEEPER-602-br3-4.patch, ZOOKEEPER-602.patch, ZOOKEEPER-602.patch,
ZOOKEEPER-602.patch, ZOOKEEPER-602.patch, ZOOKEEPER-602.patch, ZOOKEEPER-602.patch, ZOOKEEPER-602.patch
>
>
> the java code should add a ThreadGroup exception handler that logs at ERROR level any
uncaught exceptions thrown by Thread run methods.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message