You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Eric Newton (JIRA)" <ji...@apache.org> on 2015/09/29 20:48:04 UTC

[jira] [Updated] (ACCUMULO-4012) FATE lock-up

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

Eric Newton updated ACCUMULO-4012:
----------------------------------
    Affects Version/s: 1.5.3
                       1.5.4
                       1.6.0
                       1.6.2
                       1.7.0

> 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.5.3, 1.5.4, 1.6.0, 1.6.2, 1.6.3, 1.7.0
>         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)