Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 30 Oct 2014 00:11:33 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12751449.1414606538000.368572.1414627893621@Atlassian.JIRA>
In-Reply-To: <JIRA.12751449.1414606538000@Atlassian.JIRA>
References: <JIRA.12751449.1414606538000@Atlassian.JIRA>
 <JIRA.12751449.1414606538709@arcas>
Subject: [jira] [Commented] (ACCUMULO-3276) Shard.xml hung with no client
 output
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Josh Elser commented on ACCUMULO-3276:
--------------------------------------

There are a couple of places that I think we could add some additional logging (or make the existing logging more specific) to help diagnose these cases. Sadly, these were run headless, so I didn't have the ability to actually see the live system to try to figure out what was happening.

> Shard.xml hung with no client output
> ------------------------------------
>
>                 Key: ACCUMULO-3276
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3276
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.6.1
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.2, 1.7.0
>
>
> Ran Shard.xml over a 5 node instance. The only line of client output I got was that ZooSession connected to the quorum.
> 45 minutes later, my test runner timed out the module. We need more information in the client test log to actually determine where it got stuck.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)