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:32:05 UTC

[jira] [Resolved] (ACCUMULO-2219) parallelize the operation of certain FATE operations

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

Mike Drob resolved ACCUMULO-2219.
---------------------------------

    Resolution: Cannot Reproduce

[~afuchs] - if you are able to replicate this, please re-open.

> parallelize the operation of certain FATE operations
> ----------------------------------------------------
>
>                 Key: ACCUMULO-2219
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2219
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: fate
>    Affects Versions: 1.4.4, 1.5.0
>            Reporter: Adam Fuchs
>
> As in ACCUMULO-2217, a user operation can cause the FATE processor to get stuck and require administrative action to make progress on any future FATE operations. We should look at ways to parallelize the execution of FATE tasks that commute and don't interfere with each other. Maybe there are some rules we can use to run certain well-known operations in parallel (like a merge on one table at the same time as a deletion of another table, for example).
> This has a strong impact on multi-tenancy, preventing one user's operations from hosing all the other users.



--
This message was sent by Atlassian JIRA
(v6.2#6252)