[jira] [Commented] (ACCUMULO-317) Managing FATE operations is difficult

["Keith Turner (Commented) (JIRA)" <ji...@apache.org>]

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

Keith Turner commented on ACCUMULO-317:
---------------------------------------

Removed the Print command mentioned above and replaced it with the Admin command.

{noformat}
$ ./bin/accumulo org.apache.accumulo.server.fate.Admin 
Usage : Admin fail <txid> | delete <txid> | print
$ ./bin/accumulo org.apache.accumulo.server.fate.Admin print
txid: 136db1610cc74e3a  status: IN_PROGRESS      op: DeleteTable      locked: []              locking: [W:2]           top: DeleteTable
txid: 623e4ad83da848bf  status: IN_PROGRESS      op: CloneTable       locked: [W:3, R:2]      locking: []              top: FinishCloneTable
{noformat}
                
> Managing FATE operations is difficult
> -------------------------------------
>
>                 Key: ACCUMULO-317
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-317
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>             Fix For: 1.4.0
>
>
> When a FATE operation gets stuck, its hard to know whats happening.  When I first started looking into ACCUMULO-315 I knew a table operation was stuck.  But finding out which table and what operation was not easy.  Need to write a little utility that will print out information about current fate operations and table locks held by fate operations.
> It would be nice to have this before 1.4 ships as it will make debugging problems in the field easier.
> In addition to printing fate operations, we need a utility to fail and delete a fate operations (and locks). This will give a workaround to unforseen bugs in FATE operations.  When things go bad a user can try to fail the operation and if that does not work, they can delete it (which may leave the system in an inconsistent state).  Failing an operation should undo it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira