[
https://issues.apache.org/jira/browse/HDFS-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029932#comment-18029932
]
ASF GitHub Bot commented on HDFS-17164:
---------------------------------------
github-actions[bot] commented on PR #5974:
URL: https://github.com/apache/hadoop/pull/5974#issuecomment-3404077908
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> During rolling upgrade, datanode should copy-on-append when bumpReplicaGS
> -------------------------------------------------------------------------
>
> Key: HDFS-17164
> URL: https://issues.apache.org/jira/browse/HDFS-17164
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode, rolling upgrades
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Labels: pull-request-available
>
> During rolling upgrade, datanode create a trash directory for each block
> pool. Then a block deletion becomes moving the block to trash.
> For bumpReplicaGS, it will rename the meta file and then continue writing to
> the block file. It should copy the original block file and the original meta
> file to trash in order to support rollback.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
