Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 23 Jan 2014 18:42:41 +0000 (UTC)
From: "Sean Busbey (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12690844.1390502518289.2229.1390502561745@arcas>
In-Reply-To: <JIRA.12690844.1390502518289@arcas>
References: <JIRA.12690844.1390502518289@arcas>
Subject: [jira] [Created] (ACCUMULO-2244) Tracer occasionally hangs on exit
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sean Busbey created ACCUMULO-2244:
-------------------------------------

             Summary: Tracer occasionally hangs on exit
                 Key: ACCUMULO-2244
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2244
             Project: Accumulo
          Issue Type: Bug
          Components: trace
    Affects Versions: 1.4.5
         Environment: 1.4.5-SNAPSHOT on CDH4.5.0 w/gremlins
            Reporter: Sean Busbey
            Priority: Minor


When I am perturbing the availability of network components via gremlins, occasionally a tracer that has lost its zookeeper lock will hang while trying to exit.

There's nothing obvious in the logs. Jstack shows some thrift stuff around.

kill -9 on the process makes it finally exit and then restarting works like normal.

I suspect it's because of me monkeying with iptables (rather than the network failure itself). Combined with the obvious workaround, low priority.

Not sure if it impacts later versions.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)