Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 22 Jan 2013 18:50:13 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12628299.1358548113115.174200.1358880613464@arcas>
In-Reply-To: <JIRA.12628299.1358548113115@arcas>
References: <JIRA.12628299.1358548113115@arcas>
Subject: [jira] [Commented] (ACCUMULO-977) listscans and listcompaction
 commands can get stuck on bad server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on ACCUMULO-977:
---------------------------------

Integrated in Accumulo-Trunk #653 (See [https://builds.apache.org/job/Accumulo-Trunk/653/])
    ACCUMULO-977 modified listscans and listcompactions to not retry on a bad tserver (Revision 1437054)

     Result = SUCCESS
kturner : 
Files : 
* /accumulo/trunk/core/src/main/java/org/apache/accumulo/core/client/admin/InstanceOperationsImpl.java

                
> listscans and listcompaction commands can get stuck on bad server
> -----------------------------------------------------------------
>
>                 Key: ACCUMULO-977
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-977
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 1.5.0, 1.4.3
>
>
> listscans and list compactions can get stuck on a bad server.   Should timeout and print an error for that server.

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