[HADOOP-7359] Pluggable interface for cluster membership

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Travis Crawford
• Created: 04/Jun/11 17:25
• Updated: 07/Jul/11 15:17

Description

Currently Hadoop uses local files to determine cluster membership. With HDFS for example, dfs.hosts and dfs.hosts.exclude are used.

To enable tighter integrations cluster membership should be an interface, with the current file-based functionality provided as the default implementation. The common case would be no functional change, however, sites could plug an alternative implementation in, such as pulling the machine lists from a machine database.

DETAILS:

Two machine lists, includes and excludes, are used to define cluster membership and state. HostsFileReader currently handles reading these lists from files, who's names are passed in by FSNamesystem for HDFS and JobTracker for MR.

The proposed change is adding a HostsReader interface to common, and changing HostsFileReader to an abstract class that functions the same as today.

Two new classes, DFSHostsFileReader and MRHostsFileReader, extend HostsFileReader and simply pass the appropriate file names in. These new classes are needed because config key names live outside common.

Two new conf keys, defaulting to the file-based readers, would be added to choose a different hosts reader: dfs.namenode.hosts.reader.class mapreduce.jobtracker.hosts.reader.class

Comments/suggestions? I have most of this written already but would love some feedback on the general idea before posting the diff.

Issue Links

• blocks: HDFS-2035 HDFS portion of Pluggable interface for cluster membership
• blocks: MAPREDUCE-2567 MapReduce portion of Pluggable interface for cluster membership