Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C357010376 for ; Wed, 24 Jul 2013 13:09:50 +0000 (UTC) Received: (qmail 84623 invoked by uid 500); 24 Jul 2013 13:09:50 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 84386 invoked by uid 500); 24 Jul 2013 13:09:49 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 84217 invoked by uid 99); 24 Jul 2013 13:09:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jul 2013 13:09:48 +0000 Date: Wed, 24 Jul 2013 13:09:48 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-1602) put the KeyExtent in a major compactors' thread name for easier debugging MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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