accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (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 13:09:48 GMT

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

Josh Elser commented on ACCUMULO-1602:
--------------------------------------

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

Don't we already have this "concern" with listscans? If you jstack a tserver running a scan,
you have the extent in there.

I personally don't think this is a big concern. If you have the *ability* to jstack/`kill
-3` the tserver process and view the output, you likely can just print the rfile.
                
> 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