accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-1602) put the KeyExtent in thread names for easier debugging
Date Wed, 24 Jul 2013 14:33:49 GMT

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

Keith Turner updated ACCUMULO-1602:
-----------------------------------

    Description: 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.
        Summary: put the KeyExtent in thread names for easier debugging  (was: put the KeyExtent
in a compactors' thread name for easier debugging)

bq. Are you stating this as a concern about doing this or just stating it?

I think its an important consideration.  It impacts how easy it is to share a jstack of Accumulo.
 This would be an incredibly useful feature, 

We have at least three options

 # Put table id in thread name
 # Put keyextent in thread name
 # Put tablet id in thread name

I am in favor of 2 or 3.   

Considerations for #2

 * easy to immediately use the jstack output
 * may have to be edited before sharing
 * user may not edit before sharing and leak info
 * more noise when examining jstack output

Considerations for #3

 * user can immediately share jstack output when seeking help, 
 * have to take the tablet id and do a lookup somewhere to get the extent.
 * less noise when examining jstack output

Personally I am in favor of #3.  But I am not opposed to #2.
                
> 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.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

Mime
View raw message