[
https://issues.apache.org/jira/browse/HDFS-17189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029364#comment-18029364
]
ASF GitHub Bot commented on HDFS-17189:
---------------------------------------
github-actions[bot] commented on PR #6065:
URL: https://github.com/apache/hadoop/pull/6065#issuecomment-3395512506
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.
> GcTimeMonitor crashes with NegativeArraySizeException during initialization
> ---------------------------------------------------------------------------
>
> Key: HDFS-17189
> URL: https://issues.apache.org/jira/browse/HDFS-17189
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.3.6
> Reporter: ConfX
> Priority: Major
> Labels: pull-request-available
>
> The garbage collection data buffer size equals to
> `dfs.namenode.gc.time.monitor.observation.window.ms` divided by
> `dfs.namenode.gc.time.monitor.sleep.interval.ms` plus 2. When the observation
> window is a large value, the caculation overflows, resulting in a negative
> buffer size.
> To reproduce:
> 1. set `dfs.namenode.gc.time.monitor.observation.window.ms` to 945099495m
> 2. run `mvn surefire:test
> -Dtest=org.apache.hadoop.hdfs.TestHDFSFileSystemContract#testWriteReadAndDeleteHalfABlock`
> We create a PR that provides a fix by checking the computed buffer size is
> not only within `128 * 1024` but also greater than 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]
