accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4012) FATE lock-up
Date Tue, 29 Sep 2015 18:47:04 GMT

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

Eric Newton commented on ACCUMULO-4012:
---------------------------------------

ACCUMULO-1233 introduced an infinite loop to re-check Zookeeper for FATE transactions. This
has been shown to cause an infinite loop in the shell. It may also be happening in the master.
 I'm not convinced this is the only problem since restarts of the master are not known to
clear the problem.

I'm changing the infinite loop to something less scary.


> FATE lock-up
> ------------
>
>                 Key: ACCUMULO-4012
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4012
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master, tserver
>    Affects Versions: 1.6.3
>         Environment: large production cluster
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>
> On a large production cluster, some periodic data processing hangs on FATE transactions.
The basic operation is to bulk load the results of a map-reduce job into a temporary table,
which is then later deleted. Increasing the number of FATE threads has not improved the situation.
> The details are not clear, and unfortunately this system is not online, so I cannot reproduce
the logs easily, but they would be huge anyhow.



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

Mime
View raw message