[
https://issues.apache.org/jira/browse/HDFS-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759696#action_12759696
]
Konstantin Shvachko commented on HDFS-644:
------------------------------------------
test-core fails only the tests from HDFS-653
test-patch introduces one javac warning, that complains about method
DataNode.recoverBlock(), which is deprecated in ClientDatanodePortocol. It will
be removed in the next patch.
{code}
. [exec] There appear to be 108 release audit warnings before the patch and
108 release audit warnings after applying the patch.
[exec] -1 overall.
[exec] +1 @author. The patch does not contain any @author tags.
[exec] +1 tests included. The patch appears to include 12 new or
modified tests.
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec] -1 javac. The applied patch generated 111 javac compiler
warnings (more than the trunk's current 110 warnings).
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
[exec]
======================================================================
[exec]
======================================================================
[exec] Finished build.
[exec]
======================================================================
[exec]
======================================================================
{code}
> Lease recovery, concurrency support.
> ------------------------------------
>
> Key: HDFS-644
> URL: https://issues.apache.org/jira/browse/HDFS-644
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: data-node, hdfs client, name-node
> Affects Versions: Append Branch
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: Append Branch
>
> Attachments: leaseRecovery.patch
>
>
> Lease recovery happens if hdfs client does not renew its leases within an
> hour. Lease recovery triggers block recovery if the block has not been
> completed during normal write or append operations. Name-node initiates such
> block recovery by sending BlockRecoveryCommand to data-nodes (via reply to a
> heartbeat). There could be a race condition if some data-nodes still recover
> the block when the name-node decides to start a new recovery because the
> previous one did not complete. This issue should take of the race condition
> by introducing recovery ids. It should also implement the new recovery
> protocol, which is described in the append design document,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
