[HADOOP-2835] "hadoop fs -help ..." should not require a NameNode to show help messages

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Component/s: fs
• Assignee: Unassigned
• Reporter: Tsz-wo Sze
• Created: 14/Feb/08 23:56
• Updated: 08/Feb/15 17:54
• Resolved: 17/Jul/14 20:52

Description

For example, if we do "hadoop fs -help get" before started a NameNode, we will get

bash-3.2$ ./bin/hadoop fs -help get
08/02/14 15:59:52 INFO ipc.Client: Retrying connect to server: some-host:some-port. Already tried 1 time(s).
08/02/14 15:59:54 INFO ipc.Client: Retrying connect to server: some-host:some-port. Already tried 2 time(s).
08/02/14 15:59:56 INFO ipc.Client: Retrying connect to server: some-host:some-port. Already tried 3 time(s).
08/02/14 15:59:58 INFO ipc.Client: Retrying connect to server: some-host:some-port. Already tried 4 time(s).
08/02/14 16:00:00 INFO ipc.Client: Retrying connect to server: some-host:some-port. Already tried 5 time(s).
08/02/14 16:00:02 INFO ipc.Client: Retrying connect to server: some-host:some-port. Already tried 6 time(s).
08/02/14 16:00:04 INFO ipc.Client: Retrying connect to server: some-host:some-port. Already tried 7 time(s).
08/02/14 16:00:06 INFO ipc.Client: Retrying connect to server: some-host:some-port. Already tried 8 time(s).
08/02/14 16:00:08 INFO ipc.Client: Retrying connect to server: some-host:some-port. Already tried 9 time(s).
08/02/14 16:00:10 INFO ipc.Client: Retrying connect to server: some-host:some-port. Already tried 10 time(s).
Bad connection to FS. command aborted.

Issue Links

• duplicates: HADOOP-8494 bin/hadoop dfs -help tries to connect to NameNode instead of just printing help
• is duplicated by: HADOOP-8494 bin/hadoop dfs -help tries to connect to NameNode instead of just printing help
• is related to: HADOOP-5749 FsShell forces creation of default filesystem object and incorrectly uses default filesystem in some places
• is related to: HADOOP-6640 FileSystem.get() does RPC retries within a static synchronized block