You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2014/07/18 05:34:04 UTC

[jira] [Updated] (ACCUMULO-2244) Tracer occasionally hangs on exit

     [ https://issues.apache.org/jira/browse/ACCUMULO-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Drob updated ACCUMULO-2244:
--------------------------------

    Resolution: Cannot Reproduce
        Status: Resolved  (was: Patch Available)

[~busbey] - Please re-open if you see this with a later version. The 1.4 branch is EOL and will not have further development.

> 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
>         Attachments: ACCUMULO-2244.patch, tracer_18017.debug.log, tracer_18017.jstack.txt, tracer_18017.out
>
>
> 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.2#6252)