[HDFS-3946] Separate client and server uses of NN#getAddress

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.0.0-alpha
• Component/s: namenode
• Assignee: Unassigned
• Reporter: Eli Collins
• Created: 18/Sep/12 00:42
• Updated: 18/Sep/12 00:44

Description

The use of the various static NN#getAddress methods are hard to follow because they're used by by the NN itself, the DFS client, and NN related services (fsck , balancer, zkfc, etc) and the non-server NN uses (eg bootstrap standby) . They all use fs.getDefaultFS to determine the address, however in the NN case this config has been clobbered with the RPC address rather than use the core-site.xml value. In the other cases it has not. This makes it tedious to figure out things like all the various places the server side RPC addr gets used (eg in HDFS-3932 where it's set to the wildcard). This would be a lot easier to follow if the NN and client uses where separate so we could easily see where the NN is determining it's address (and using the clobbered value) and where the clients are determining it (and using the core-site value).

Issue Links

• is related to: HDFS-3932 NameNode Web UI broken if the rpc-address is set to the wildcard