[HDFS-14017] ObserverReadProxyProviderWithIPFailover should work with HA configuration

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: HDFS-12943, 3.3.0
• Target Version/s: HDFS-12943
• Assignee: Chen Liang
• Reporter: Chen Liang
• Created: 22/Oct/18 19:59
• Updated: 24/Dec/18 18:22
• Resolved: 17/Nov/18 01:31

Description

Currently ObserverReadProxyProviderWithIPFailover extends ObserverReadProxyProvider, and the only difference is changing the proxy factory to use IPFailoverProxyProvider. However this is not enough because when calling constructor of ObserverReadProxyProvider in super(...), the follow line:

nameNodeProxies = getProxyAddresses(uri,
        HdfsClientConfigKeys.DFS_NAMENODE_RPC_ADDRESS_KEY);

will try to resolve the all configured NN addresses to do configured failover. But in the case of IPFailover, this does not really apply.

 

A second issue closely related is about delegation token. For example, in current IPFailover setup, say we have a virtual host nn.xyz.com, which points to either of two physical nodes nn1.xyz.com or nn2.xyz.com. In current HDFS, there is always only one DT being exchanged, which has hostname nn.xyz.com. Server only issues this DT, and client only knows the host nn.xyz.com, so all is good. But in Observer read, even with IPFailover, the client will no longer contacting nn.xyz.com, but will actively reaching to nn1.xyz.com and nn2.xyz.com. During this process, current code will look for DT associated with hostname nn1.xyz.com or nn2.xyz.com, which is different from the DT given by NN. causing Token authentication to fail. This happens in AbstractDelegationTokenSelector#selectToken. New IPFailover proxy provider will need to resolve this as well.