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 DEA2317F2F for ; Thu, 14 May 2015 22:20:04 +0000 (UTC) Received: (qmail 10538 invoked by uid 500); 14 May 2015 22:18:32 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 10410 invoked by uid 500); 14 May 2015 22:18:32 -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 10386 invoked by uid 99); 14 May 2015 22:18:31 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 May 2015 22:18:31 +0000 Date: Thu, 14 May 2015 22:18:31 +0000 (UTC) From: "Ed Coleman (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3807) Log Recovery Copy/Sort progress exceeds 100% 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-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544394#comment-14544394 ] Ed Coleman commented on ACCUMULO-3807: -------------------------------------- I agree with [~ctubbsii] having progress sit at %100 is worse than a moving indicator with funny looking numbers. Having numbers > than 100% does look odd, but as long as it is moving it reflects that recovery is working and will eventually (hopefully) complete. If it was clamped at 100% and then hung for any significant amount of time (maybe > 30 seconds), well I'm likely to start to panic that something else is wrong with the system. First, something happened that caused log recovery, and now log recovery is hanging.... With 1.4.x versions I seem to recall recovery taking minutes in "bad" cases. If the recovery indicator was at 100% for that amount of time it would certainly cause me concern. Maybe instead of a %, the number shown is # copy / sort operations? While it would be nice to know about how long things were going to take, if it can be estimated - otherwise it seems more important to provide feedback and reflect that things are still progressing - whatever form that is. > Log Recovery Copy/Sort progress exceeds 100% > -------------------------------------------- > > Key: ACCUMULO-3807 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3807 > Project: Accumulo > Issue Type: Improvement > Components: monitor > Reporter: Josh Elser > Priority: Minor > Labels: newbie > Fix For: 1.6.3, 1.8.0, 1.7.1 > > > I regularly notice that the Copy/Sort progress bar for log recovery on the monitor exceeds 100%. We should either > * Find out why this exceeds 100% and fix the computation > or > * Just cap the value so that it just reports 100% and doesn't exceed it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)