[HDFS-15621] Datanode DirectoryScanner uses excessive memory

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.3.1, 3.4.0, 3.2.3
• Component/s: datanode
• Labels: pull-request-available
• Target Version/s: 3.4.0
• Hadoop Flags: Reviewed
• Assignee: Stephen O'Donnell
• Reporter: Stephen O'Donnell
• Created: 09/Oct/20 14:19
• Updated: 27/Jan/24 03:06
• Resolved: 26/Apr/21 11:58

Description

We generally work a rule of 1GB heap on a datanode per 1M blocks. For nodes with a lot of blocks, this can mean a lot of heap.

We recently captured a heapdump of a DN with about 22M blocks and found only about 1.5GB was occupied by the ReplicaMap. Another 9GB of the heap is taken by the DirectoryScanner ScanInfo objects. Most of this memory was alloated to strings.

Checking the strings in question, we can see two strings per scanInfo, looking like:

/current/BP-671271071-10.163.205.13-1552020401842/current/finalized/subdir28/subdir17/blk_1180438785
_106716708.meta

I will update a screen shot from MAT showing this.

For the first string especially, the part "/current/BP-671271071-10.163.205.13-1552020401842/current/finalized/" will be the same for every block in the block pool as the scanner is only concerned about finalized blocks.

We can probably also store just the subdir indexes "28" and "27" rather than "subdir28/subdir17" and then construct the path when it is requested via the getter.

Issue Links

• relates to: HDFS-14531 Datanode's ScanInfo requires excessive memory
• links to: GitHub Pull Request #2849