[
https://issues.apache.org/jira/browse/ACCUMULO-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Newton resolved ACCUMULO-4012.
-----------------------------------
Resolution: Fixed
I'm closing this as fixed, but I believe that ACCUMULO-4028 is the root cause
of the symptoms we saw. I still believe that the inf. loop was too aggressive.
> 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
> Fix For: 1.6.5, 1.7.1, 1.8.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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)
