hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-8394) Utilize isFileClosed() so that the wait for lease recovery can be optimized
Date Tue, 23 Apr 2013 05:21:16 GMT

     [ https://issues.apache.org/jira/browse/HBASE-8394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-8394.
--------------------------

    Resolution: Incomplete

This API is not in hdfs 1.1 nor in 2.0.  I do not know how the API is supposed to help. Do
I have to go research in referenced issues?  Read source code?  The issue is about lease recovery?
 Do I not call lease recovery if isFileClosed says it is closed?

Closing as incomplete.  After spending some time hereabouts I cannot tell what this issue
is about.  The edit above does little to clarify.
                
> Utilize isFileClosed() so that the wait for lease recovery can be optimized
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-8394
>                 URL: https://issues.apache.org/jira/browse/HBASE-8394
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>
> In HDFS-4525, the following API was added:
> {code}
>   /**
>    * Get the close status of a file
>    * @param src The path to the file
>    *
>    * @return return true if file is closed
>    * @throws FileNotFoundException if the file does not exist.
>    * @throws IOException If an I/O error occurred     
>    */
>   public boolean isFileClosed(Path src) throws IOException {
> {code}
> It is not available in hadoop 1.1 at the moment.
> In HBASE-8389, there was discussion for utilizing isFileClosed() to optimize the wait
time for lease recovery.
> Subsequent lease recovery request for the same Path would preempt outstanding recovery.
But if we wait for one particular recovery request to complete without limit on duration,
we may incur penalty due to various failure scenarios such as the primary Data Node chosen
by Namenode being stale, etc.
> This JIRA continues the work for 0.95 / trunk.

--
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