Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
3.0.0-alpha1
-
None
-
None
-
None
Description
Each hadoop command is printing an INFO message about a setsid exit code. This is at best annoying, and it prevents the start-dfs.sh startup script from working properly since the INFO message is interpreted as more namenode hosts to connect to. start-dfs.sh uses hdfs getconf -namenodes which like other hadoop commands prints the extra INFO message. For example:
$ hdfs getconf -namenodes 2013-05-06 20:11:22,096 INFO [main] util.Shell (Shell.java:isSetsidSupported(311)) - setsid exited with exit code 0 localhost
Attachments
Issue Links
- duplicates
-
HADOOP-9593 stack trace printed at ERROR for all yarn clients without hadoop.home set
- Closed
- is broken by
-
YARN-493 NodeManager job control logic flaws on Windows
- Closed
- is related to
-
HDFS-4427 start-dfs.sh generates malformed ssh command when not running with native libs
- Open