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 30E3210477 for ; Tue, 23 Jul 2013 20:42:49 +0000 (UTC) Received: (qmail 8546 invoked by uid 500); 23 Jul 2013 20:42:49 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 8518 invoked by uid 500); 23 Jul 2013 20:42: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 8509 invoked by uid 99); 23 Jul 2013 20:42:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jul 2013 20:42:49 +0000 Date: Tue, 23 Jul 2013 20:42:48 +0000 (UTC) From: "Mike Drob (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=13717584#comment-13717584 ] Mike Drob commented on ACCUMULO-1602: ------------------------------------- I am not a fan of a utility that, in essence, is running a brute force attack on the hash that we're trying to find. This also puts up a huge barrier to the usefulness of the naming. Why are we even worrying about this? Is there a max length to thread names that we need to fit in? What are the semantics for automatic expansion in a range compaction? Does it include the whole row? The whole tablet? Is this part of the API contract and specified in the docs, or is it simply a side-effect of the implementation? > 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