[YARN-1912] ResourceLocalizer started without any jvm memory control

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: nodemanager
• Labels: BB2015-05-RFC
• Target Version/s: 2.8.0
• Assignee: Masatake Iwasaki
• Reporter: stanley shi
• Created: 08/Apr/14 08:51
• Updated: 30/Aug/16 01:31
• Resolved: 09/May/15 03:03

Description

In the LinuxContainerExecutor.java#startLocalizer, it does not specify any "-Xmx" configurations in the command, this caused the ResourceLocalizer to be started with default memory setting.
In an server-level hardware, it will use 25% of the system memory as the max heap size, this will cause memory issue in some cases.