[
https://issues.apache.org/jira/browse/HDFS-17850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18103565#comment-18103565
]
ASF GitHub Bot commented on HDFS-17850:
---------------------------------------
deepujain commented on PR #8334:
URL: https://github.com/apache/hadoop/pull/8334#issuecomment-5249085423
No code changes in this update. On the August 10, 2026 head, Apache Yetus
and `continuous-integration/jenkins/pr-merge` are green; the only remaining red
signal was the fork-side GitHub `Build`, where the failing shard was `Run /
Test common (Java 17) ubuntu_24-trunk` with
`TestZKDelegationTokenSecretManager.testNodesLoadedAfterRestart` failing and
`TestHttpServer.testHttpServer2Metrics` showing up as a flake. That still looks
outside this append-generation-stamp patch, so I reran the existing fork-side
`Build` workflow on August 11, 2026 for a fresh signal.
> During append, it is necessary to verify whether the same GS exists in the
> datanode.
> ------------------------------------------------------------------------------------
>
> Key: HDFS-17850
> URL: https://issues.apache.org/jira/browse/HDFS-17850
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: TangLin
> Priority: Major
> Labels: pull-request-available
>
> When using a third-party HDFS client, if there is a problem with the client
> logic and append does not update the GS, HDFS may report corrupted replicas.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
