accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2219) parallelize the operation of certain FATE operations
Date Tue, 21 Jan 2014 15:21:19 GMT

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

Keith Turner commented on ACCUMULO-2219:
----------------------------------------

Yeah, need more info.  Its possible the 2nd fate operation was stuck
waiting for something to happen on a tablet server.  The output of the fate
admin command and a jstack of the master would be a good start.





> 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.1.5#6160)

Mime
View raw message