[HDFS-13248] RBF: Namenode need to choose block location for the client

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0, 2.10.2, 3.3.5
• Fix Version/s: 3.4.0, 2.10.2, 3.3.5
• Component/s: rbf
• Labels: pull-request-available
• Target Version/s: 3.4.0, 2.10.2, 3.3.5
• Hadoop Flags: Reviewed
• Assignee: Owen O'Malley
• Reporter: Wu Weiwei
• Created: 08/Mar/18 09:26
• Updated: 12/Feb/24 06:38
• Resolved: 21/Mar/22 17:30

Description

When execute a put operation via router, the NameNode will choose block location for the router, not for the real client. This will affect the file's locality.

I think on both NameNode and Router, we should add a new addBlock method, or add a parameter for the current addBlock method, to pass the real client information.

Issue Links

• duplicates: HDFS-16015 RBF: Read and write data through router select dn according to real user ip
• is related to: HDFS-16756 RBF proxies the client's user by the login user to enable CacheEntry
• relates to: HDFS-13293 RBF: The RouterRPCServer should transfer client IP via CallerContext to NamenodeRpcServer
• relates to: HADOOP-16254 Add proxy address in IPC connection
• links to: GitHub Pull Request #4081