You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Vinayakumar B (JIRA)" <ji...@apache.org> on 2017/07/11 16:14:00 UTC
[jira] [Assigned] (HDFS-12120) Use new block for pre-RollingUpgrade
files` append requests
[ https://issues.apache.org/jira/browse/HDFS-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinayakumar B reassigned HDFS-12120:
------------------------------------
Assignee: Vinayakumar B
> Use new block for pre-RollingUpgrade files` append requests
> -----------------------------------------------------------
>
> Key: HDFS-12120
> URL: https://issues.apache.org/jira/browse/HDFS-12120
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Vinayakumar B
> Assignee: Vinayakumar B
>
> After the RollingUpgrade prepare, append on pre-RU files will re-open the same last block and makes changes to it (appending extra data, changing genstamp etc).
> These changes to the block will not be tracked in Datanodes (either in trash or via hardlinks)
> This creates problem if RollingUpgrade.Rollback is called.
> Since block state and size both changed, after rollback block will be marked corrupted.
> To avoid this, first time append on pre-RU files can be forced to write to new block itself.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org