hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10000) Initiate lease recovery for outstanding WAL files at the very beginning of recovery
Date Sun, 24 Nov 2013 04:38:36 GMT

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

stack commented on HBASE-10000:
-------------------------------

bq. The code modifies two local variables. Making it a method means changing findIsFileClosedMeth
to AtomicBoolean. Is this what you meant ?

They probably shouldn't be local variables?  Why do reflection every time this method is called?
 Why not save off if method is available or not and if you've looked for it or not.

> Initiate lease recovery for outstanding WAL files at the very beginning of recovery
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-10000
>                 URL: https://issues.apache.org/jira/browse/HBASE-10000
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>             Fix For: 0.98.0
>
>         Attachments: 10000-v1.txt, 10000-v4.txt, 10000-v5.txt
>
>
> At the beginning of recovery, master can send lease recovery requests concurrently for
outstanding WAL files using a thread pool.
> Each split worker would first check whether the WAL file it processes is closed.
> Thanks to Nicolas Liochon and Jeffery discussion with whom gave rise to this idea. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message