[
https://issues.apache.org/jira/browse/HDFS-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868783#action_12868783
]
Todd Lipcon commented on HDFS-1142:
-----------------------------------
bq. May be setting harld_limit = soft_limit will help with fencing. It seems
this is the behavior you are looking for.
Since this is a cluster-wide setting I don't think it's a good idea. We only
want this kind of lease-stealing behavior for hlog recovery - for other normal
HDFS access, we definitely want the original lease holder to be able to renew
its lease after soft limit has elapsed (assuming that no one else has tried to
steal it)
> 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.
