Details
-
Bug
-
Status: Open
-
Critical
-
Resolution: Unresolved
-
2.5.2
-
None
-
None
-
None
Description
Hi,
We have noticed that with a small typo in terms of xml config (mapred-site.xml) can cause the nodemanager go down completely without stopping/restarting it externally.
I find it little weird that editing the config files on the filesystem, could cause the running slave daemon yarn nodemanager shutdown.
In this case, I had a ending tag '/' missed in a property and that induced the nodemanager go down in a cluster.
Why would nodemanager reload the configs while it is running? Are not they picked up when they are started? Even if they are automated to pick up the new configs dynamically, I think the xmllint/config checker should come in before the nodemanager is asked to reload/restart.
—
java.lang.RuntimeException: org.xml.sax.SAXParseException; systemId: file:/etc/hadoop/conf/mapred-site.xml; lineNumber: 228; columnNumber: 3; The element type "value" must be terminated by the matching end-tag "</value>".
at org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2348)
—
Please shed light on this.