[
https://issues.apache.org/jira/browse/HDFS-17850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102376#comment-18102376
]
ASF GitHub Bot commented on HDFS-17850:
---------------------------------------
deepujain commented on PR #8334:
URL: https://github.com/apache/hadoop/pull/8334#issuecomment-5202672431
No code changes here. Yetus on the August 5, 2026 head failed only in
`TestBlockRecoveryCauseStandbyNameNodeCrash`, but that test passes locally on
the current branch with
`JAVA_HOME=/opt/homebrew/opt/openjdk@17/libexec/openjdk.jdk/Contents/Home
PATH=/opt/homebrew/opt/openjdk@17/libexec/openjdk.jdk/Contents/Home/bin:$PATH
./mvnw -Dmaven.repo.local=/private/tmp/hadoop-m2 test -pl
hadoop-hdfs-project/hadoop-hdfs -am
-Dtest=TestBlockRecoveryCauseStandbyNameNodeCrash -DskipTests=false` (1 test, 0
failures). I pushed a no-code `Trigger CI` commit to give Yetus and `pr-merge`
a fresh run.
> 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]
