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

Posted to notifications@accumulo.apache.org by "Eric Newton (JIRA)" <ji...@apache.org> on 2013/07/24 21:13:48 UTC

[jira] [Resolved] (ACCUMULO-1602) put the KeyExtent in thread names for easier debugging

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

Eric Newton resolved ACCUMULO-1602.
-----------------------------------

    Resolution: Fixed

I mirrored what scans already do: I put the key extent in the thread name
                
> put the KeyExtent in thread names for easier debugging
> ------------------------------------------------------
>
>                 Key: ACCUMULO-1602
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1602
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>            Reporter: Eric Newton
>            Priority: Minor
>              Labels: newbie
>             Fix For: 1.5.1, 1.6.0
>
>
> When a thread is stuck doing an operation on a tablet, it would be nice to know which tablet.  One easy way to do this is to change the thread name to include this information so it available in jstack. Scans and compactions could do this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira