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 Fri, 21 May 2010 18:23:18 GMT

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

Konstantin Shvachko commented on HDFS-1142:

If the file is closed nobody can transparently regain the lease, because closed files don't
have leases. I understand transparently as by calling write or flush, but without reopening
it. So the answer to the question

> if the recovering process wins, opens the file for append, and immediately closes it.
Are we guaranteed then that another flush() call from the client at that point would definitely

is Yes. 

I think Dhruba meant that if the recovering process closes the file, then the old client can
access it by reopening it. But this is not transparent if my understanding of transparency
is the same as yours.

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

View raw message