[
https://issues.apache.org/jira/browse/HDFS-16284?focusedWorklogId=701075&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-701075
]
ASF GitHub Bot logged work on HDFS-16284:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Dec/21 02:20
Start Date: 25/Dec/21 02:20
Worklog Time Spent: 10m
Work Description: Cosss7 commented on pull request #3586:
URL: https://github.com/apache/hadoop/pull/3586#issuecomment-1000960393
> Hi @Cosss7, can you fix the checkstyle warn? Thanks.
OK, update soon.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 701075)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
