You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/01/02 18:01:13 UTC

[jira] [Commented] (CURATOR-177) Pull request: Use Curator in thread names

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

ASF GitHub Bot commented on CURATOR-177:
----------------------------------------

Github user swankjesse commented on the pull request:

    https://github.com/apache/curator/pull/60#issuecomment-68542197
  
    https://issues.apache.org/jira/browse/CURATOR-177


> Pull request: Use Curator in thread names
> -----------------------------------------
>
>                 Key: CURATOR-177
>                 URL: https://issues.apache.org/jira/browse/CURATOR-177
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Framework, General
>    Affects Versions: 2.7.0
>            Reporter: Jesse Wilson
>            Priority: Minor
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> I do thread dumps on my servers to look out for runaway thread pools. Curator's thread names aren't necessarily very helpful at figuring out what's going on. This should make that easier.
> (ZooKeeper itself is also guilty here.)
> https://github.com/apache/curator/pull/60



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