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] [Commented] (ACCUMULO-1602) put the KeyExtent in a major compactors' thread name for easier debugging
Date Wed, 24 Jul 2013 12:53:49 GMT

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

Keith Turner commented on ACCUMULO-1602:
----------------------------------------

bq. Why are we even worrying about this? Is there a max length to thread names that we need
to fit in?

I look a the output of jstack alot and did not like the idea of a really long thread name.
 But thats just my preference.  I looked at the current KeyExtent toString().  The max length
it will print is around 160 to 170 bytes.  Of course that could be modified to make it truncate
more.

Another thing to consider is that jstack output is shared for debugging purposes.  If the
jstack contained KeyExtents, then it possible it contains data from a table.  A user may inadvertently
share data from their table that they did not want to when sharing a jstack.


                
> put the KeyExtent in a major compactors' thread name 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
>
>


--
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