[
https://issues.apache.org/jira/browse/HADOOP-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated HADOOP-3310:
-------------------------------------------
Attachment: 3310_20080522b.patch
3310_20080522b.patch:
- fixed the typo, item 2 and item 3 mentioned above
- added targets in INodeFileUnderConstruction
- renew lease even if all targets are not avaliable
- In FSDataset.updateBlock, unpdate oldblock.generationStamp before using it.
- In LeaseManager.syncBlock, if successList.isEmpty(), don't commit the block.
- In FSNamesystem.commitBlockSynchronization, don't write to editLog since the
finalizeINodeFileUnderConstruction(...) has already done it.
> Lease recovery for append
> -------------------------
>
> Key: HADOOP-3310
> URL: https://issues.apache.org/jira/browse/HADOOP-3310
> Project: Hadoop Core
> Issue Type: New Feature
> Components: dfs
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Tsz Wo (Nicholas), SZE
> Attachments: 3310_20080514.patch, 3310_20080516b.patch,
> 3310_20080516c.patch, 3310_20080519.patch, 3310_20080519b.patch,
> 3310_20080520.patch, 3310_20080521.patch, 3310_20080522b.patch
>
>
> In order to support file append, a GenerationStamp is associated with each
> block. Lease recovery will be performed when there is a possibility that the
> replicas of a block in a lease may have different GenerationStamp values.
> For more details, see the documentation in HADOOP-1700.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.