[
https://issues.apache.org/jira/browse/ACCUMULO-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188564#comment-13188564
]
Keith Turner commented on ACCUMULO-317:
---------------------------------------
I modified the CloneTable operation so that it would get stuck, cloned a table,
and deleted the table I was trying to clone. Then I ran the new print util and
its output is below. I killed the master and fixed the clone table operation
and it all ran.
{noformat}
$ ./bin/accumulo org.apache.accumulo.server.fate.Print
txid: 5c9c7a705293008f status: IN_PROGRESS op: DeleteTable locked:
[] locking: [W:2] top: DeleteTable
txid: 4830c0e4d610a7a3 status: IN_PROGRESS op: CloneTable locked:
[W:3, R:2] locking: [] top: FinishCloneTable
{noformat}
> Debugging 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.
--
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
