[YARN-10266] Setting debug delay to a too high number will cause NM fail to start

• Type: Bug
• Status: Resolved
• Priority: Trivial
• Resolution: Won't Fix
• Affects Version/s: 3.3.0
• Component/s: yarn
• Labels: newbie
• Target Version/s: 3.4.0
• Assignee: Adam Antal
• Reporter: Adam Antal
• Created: 14/May/20 16:24
• Updated: 01/Jul/20 10:40
• Resolved: 01/Jul/20 10:40

Description

If I set some inappropriate number for yarn.nodemanager.delete.debug-delay-sec, I'd rather have functional nM with some ERROR messages in the log stating that it has been disabled due to illegal argument, than to have a failed NM.

Stack trace:

java.lang.NumberFormatException: For input string: "99999999999"
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
	at java.lang.Integer.parseInt(Integer.java:583)
	at java.lang.Integer.parseInt(Integer.java:615)
	at org.apache.hadoop.conf.Configuration.getInt(Configuration.java:1509)
	at org.apache.hadoop.yarn.server.nodemanager.DeletionService.serviceInit(DeletionService.java:179)
	at org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
	at org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:108)
	at org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceInit(NodeManager.java:478)
	at org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
	at org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:936)
	at org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:1016)