You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@accumulo.apache.org by "Eric Newton (Commented) (JIRA)" <ji...@apache.org> on 2012/01/18 02:49:40 UTC

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

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

Eric Newton commented on ACCUMULO-317:
--------------------------------------

+1 for making the support easier
                
> 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