[MAPREDUCE-5380] Invalid mapred command should return non-zero exit code

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.4-alpha, 3.0.0-alpha1
• Fix Version/s: 0.23.10, 2.3.0
• Hadoop Flags: Reviewed
• Assignee: Stephen Chu
• Reporter: Stephen Chu
• Created: 10/Jul/13 22:25
• Updated: 12/May/16 18:23
• Resolved: 17/Jul/13 00:33

Description

Running the mapred bin script with an invalid command returns exit code 0, but it should return a non-zero exit code.

[schu@hdfs-snapshots-1 ~]$ hadoop-3.0.0-SNAPSHOT/bin/mapred gibberish
gibberish - invalid command
Usage: mapred [--config confdir] COMMAND
       where COMMAND is one of:
  pipes                run a Pipes job
  job                  manipulate MapReduce jobs
  queue                get information regarding JobQueues
  classpath            prints the class path needed for running
                       mapreduce subcommands
  historyserver        run job history servers as a standalone daemon
  distcp <srcurl> <desturl> copy file or directories recursively
  archive -archiveName NAME -p <parent path> <src>* <dest> create a hadoop archive

Most commands print help when invoked w/o parameters.
[schu@hdfs-snapshots-1 ~]$ echo $?
0
[schu@hdfs-snapshots-1 ~]$