[
https://issues.apache.org/jira/browse/HDFS-16284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuxuan Wang updated HDFS-16284:
-------------------------------
Description:
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.
was:
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 in
> 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: 10m
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
