[ https://issues.apache.org/jira/browse/HADOOP-11543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309419#comment-14309419 ]
Allen Wittenauer commented on HADOOP-11543: ------------------------------------------- You folks are basically helping me to confirm that my conviction to stop committing to branch-2 is a good one. :D The problem here is that the --loglevel option isn't being handled by yarn-config.sh like it is in hadoop-config.sh. This is purely a branch-2 problem since trunk's shell rewrite consolidated almost all of that functionality. As it stands, the --loglevel option in the usage message as of this last commit: a) doesn't work in the case of yarn b) is a bad message because it doesn't actually hint that loglevel takes a parameter Additionally, in the case of trunk, I think a follow to HADOOP-11495 might be to drop *all* of the -- parameters from the usage messages, put [GENERIC SHELL OPTS] (or something) in place, and point folks to the documentation or provider a helper function in hadoop-functions.sh that prints them all out, maybe tied to a --extendedhelp or if a user specifically calls help|h|? . > Improve help message for hadoop/yarn command > -------------------------------------------- > > Key: HADOOP-11543 > URL: https://issues.apache.org/jira/browse/HADOOP-11543 > Project: Hadoop Common > Issue Type: Improvement > Components: scripts > Affects Versions: 2.6.0 > Reporter: Jagadesh Kiran N > Assignee: Brahma Reddy Battula > Priority: Trivial > Fix For: 2.7.0 > > Attachments: HADOOP-11543-001.patch, HADOOP-11543-002.patch, > HADOOP-11543-002.patch, HADOOP-11543-branch-2-003.patch, > HADOOP-11543-branch-2.001.patch, HADOOP-11543-branch-2.002, > HADOOP-11543.patch, OrinYarncommnad.png, YARN-3128-01.patch, YARN-3128.patch > > > Pls check the snapshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)