accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1077) Deadlock possible with log recovery.
Date Sat, 02 Mar 2013 05:29:14 GMT

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

Josh Elser commented on ACCUMULO-1077:
--------------------------------------

I'm a little confused... With the changes to HadoopLogCloser, I tried building against CDH3u5,
but got an error because, in CDH3u5, DistributedFileSystem#recoverLease throws NoSuchMethodException.
0.20.205, 1.0.4, 1.1.3, nor 2.0.2-alpha have throws NoSuchMethodException, though.

Modifying the CDH3u5 source gets around the Accumulo compilation issue. I'm not sure there's
any good way around it, but perhaps I'm just noting it here.
                
> Deadlock possible with log recovery.
> ------------------------------------
>
>                 Key: ACCUMULO-1077
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1077
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Keith Turner
>            Assignee: Keith Turner
>            Priority: Blocker
>             Fix For: 1.5.0
>
>
> The master enqueues a FATE operation to start log recovery.  If all FATE threads are
busy trying to read the metadata table and the metadata table needs to be recovered then we
are stuck.  I think this bug may be new in 1.5, but I am not sure.  Need to check if it exists
in 1.4.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message