hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1142) Lease recovery doesn't reassign lease when triggered by append()
Date Tue, 25 May 2010 23:31:36 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871432#action_12871432
] 

Konstantin Shvachko commented on HDFS-1142:
-------------------------------------------

Thanks. Yes with 0.20 that would be a completely different issue. I did not closely follow
the latest developments with sync(). Dhruba would know this better. 
There should be no violation for hflush(): if the old client renews the lease it will reset
the blockRecoveryId, and the lease recovery that started before that will fail - no big deal.
I'll create a jira to investigate my findings in 0.22 (21).

> Lease recovery doesn't reassign lease when triggered by append()
> ----------------------------------------------------------------
>
>                 Key: HDFS-1142
>                 URL: https://issues.apache.org/jira/browse/HDFS-1142
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.21.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hdfs-1142.txt, hdfs-1142.txt
>
>
> If a soft lease has expired and another writer calls append(), it triggers lease recovery
but doesn't reassign the lease to a new owner. Therefore, the old writer can continue to allocate
new blocks, try to steal back the lease, etc. This is for the testRecoveryOnBlockBoundary
case of HDFS-1139

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message