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 D18A610A0A for ; Thu, 18 Dec 2014 03:54:15 +0000 (UTC) Received: (qmail 75822 invoked by uid 500); 18 Dec 2014 03:54:15 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 75779 invoked by uid 500); 18 Dec 2014 03:54:15 -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 75659 invoked by uid 99); 18 Dec 2014 03:54:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Dec 2014 03:54:15 +0000 Date: Thu, 18 Dec 2014 03:54:15 +0000 (UTC) From: "Corey J. Nolet (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-2837) Scanning empty table can be optimized 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-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Corey J. Nolet updated ACCUMULO-2837: ------------------------------------- Fix Version/s: (was: 1.6.2) 1.6.3 > Scanning empty table can be optimized > ------------------------------------- > > Key: ACCUMULO-2837 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2837 > Project: Accumulo > Issue Type: Bug > Affects Versions: 1.6.0 > Reporter: Keith Turner > Assignee: Keith Turner > Priority: Trivial > Fix For: 1.7.0, 1.6.3 > > > I wrote an application that repeatedly scanned random rows in an empty table at one point. It did not know the table was empty. I was jstacking the tserver and repeatedly saw stack traces in a few places in the code. > * the audit canScan method > * DefaultConfiguration.get > * Kept seeing Password token ungziping the password?????? > After fixing all of these issues (except for system token) I ran a simple test I saw times go from ~1.7s to ~1.3s for a simple test I wrote to recreate this issue. > I am not sure how much of an impact the gziping the password has. I was just sampling the stack traces manually. I seems like I saw the password token gzip stack traces less frequently, but I did catch it multiple jstack calls. -- This message was sent by Atlassian JIRA (v6.3.4#6332)