Rakesh R created ZOOKEEPER-1907:
-----------------------------------
Summary: Improve Thread handling
Key: ZOOKEEPER-1907
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1907
Project: ZooKeeper
Issue Type: Improvement
Components: server
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 3.5.0
Server has many critical threads running and co-ordinating each other like
RequestProcessor chains et. When going through each threads, most of them
having the similar structure like:
{code}
public void run() {
try {
while(running)
// processing logic
}
} catch (InterruptedException e) {
LOG.error("Unexpected interruption", e);
} catch (Exception e) {
LOG.error("Unexpected exception", e);
}
LOG.info("...exited loop!");
}
{code}
>From the design I could see, there could be a chance of silently leaving the
>thread by swallowing the exception. If this happens in the production, the
>server would get hanged forever and would not be able to deliver its role. Now
>its hard for the management tool to detect this.
The idea of this JIRA is to discuss and imprv.
Reference: [Community discussion
thread|http://mail-archives.apache.org/mod_mbox/zookeeper-user/201403.mbox/%3cc2496325850aa74c92aaf83aa9662d26458a1...@szxeml561-mbx.china.huawei.com%3E]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
