[HADOOP-7154] Should set MALLOC_ARENA_MAX in hadoop-config.sh

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.22.0
• Fix Version/s: 1.0.4, 0.22.0
• Component/s: scripts
• Hadoop Flags: Reviewed
• Assignee: Todd Lipcon
• Reporter: Todd Lipcon
• Created: 25/Feb/11 00:48
• Updated: 21/Apr/15 21:28
• Resolved: 08/Mar/11 23:51

Description

New versions of glibc present in RHEL6 include a new arena allocator design. In several clusters we've seen this new allocator cause huge amounts of virtual memory to be used, since when multiple threads perform allocations, they each get their own memory arena. On a 64-bit system, these arenas are 64M mappings, and the maximum number of arenas is 8 times the number of cores. We've observed a DN process using 14GB of vmem for only 300M of resident set. This causes all kinds of nasty issues for obvious reasons.

Setting MALLOC_ARENA_MAX to a low number will restrict the number of memory arenas and bound the virtual memory, with no noticeable downside in performance - we've been recommending MALLOC_ARENA_MAX=4. We should set this in hadoop-env.sh to avoid this issue as RHEL6 becomes more and more common.

Issue Links

• relates to: MAPREDUCE-3068 Should set MALLOC_ARENA_MAX for all YARN daemons and AMs/Containers
• relates to: HBASE-5529 MR test failures becuase MALLOC_ARENA_MAX is not set