[
https://issues.apache.org/jira/browse/HDFS-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875303#action_12875303
]
sam rash commented on HDFS-1142:
--------------------------------
a small sidenote:
re: killing writers, it does so *after* getting metadata, so there is still a
window under which the client could start another lease recovery, it would
complete, and it could start writing and call sync. the 1st lease recovery
kills threads, then truncate the block (based on the first set of lengths).
This violates sync/hflush semantics. I don't know if there's a jira for this,
but I had planned to make the change so the writers *are* killed first thing
before getting meta-data.
> 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.
