[
https://issues.apache.org/jira/browse/HDFS-16284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18040020#comment-18040020
]
ASF GitHub Bot commented on HDFS-16284:
---------------------------------------
github-actions[bot] commented on PR #3586:
URL: https://github.com/apache/hadoop/pull/3586#issuecomment-3565083626
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.
> Unboxing long value in old version's block report cause full GC
> ---------------------------------------------------------------
>
> Key: HDFS-16284
> URL: https://issues.apache.org/jira/browse/HDFS-16284
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Yuxuan Wang
> Assignee: Yuxuan Wang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When upgrade cluster from 2.6 to 3.1, namenode fall into full GC trouble.
> NN run 3.1 version and DN run 2.6 version, block report type is longs not PB
> introduced by https://issues.apache.org/jira/browse/HDFS-7435 . So it's run
> into LongDecoder.
> We find change
> org.apache.hadoop.hdfs.protocol.BlockListAsLongs.LongsDecoder#values type
> from List<Long> to long[] can fix the issue, but I can't for sure that the
> Long unboxing cause full GC problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
