[
https://issues.apache.org/jira/browse/HDFS-17196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029134#comment-18029134
]
ASF GitHub Bot commented on HDFS-17196:
---------------------------------------
github-actions[bot] commented on PR #6091:
URL: https://github.com/apache/hadoop/pull/6091#issuecomment-3392652802
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.
> Overflow during getDatanodeReadTimeout
> --------------------------------------
>
> Key: HDFS-17196
> URL: https://issues.apache.org/jira/browse/HDFS-17196
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.3.6
> Reporter: ConfX
> Priority: Major
> Labels: pull-request-available
>
> Datanode read timeout equals to READ_TIMEOUT_EXTENSION * numNodes +
> `dfs.client.socket-timeout`. A large
> dfs.client.socket-timeout/numNodes/READ_TIMEOUT_EXTENSION will cause overflow.
>
> To reproduce:
> 1. set `dfs.client.socket-timeout` to 2147483646
> 2. run `mvn surefire:test
> -Dtest=org.apache.hadoop.hdfs.server.namenode.ha.TestHASafeMode#testBlocksRemovedWhileInSafeModeEditsArriveFirst`
>
> We create a PR that provides a fix by checking the read timeout calculation
> is at least 0.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
