[HDFS-13293] RBF: The RouterRPCServer should transfer client IP via CallerContext to NamenodeRpcServer

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.4.0, 3.3.5
• Component/s: rbf
• Labels: pull-request-available
• Assignee: Hui Fei
• Reporter: Baolong Mao
• Created: 15/Mar/18 14:39
• Updated: 23/Feb/23 10:57
• Resolved: 09/Oct/20 11:28

Description

Otherwise, the namenode don't know the client's callerContext

This jira focuses on audit log which logs real client ip. Leave locality to HDFS-13248

Issue Links

• blocks: HDFS-13986 RBF: Integrate security changes with audit logging.
• breaks: HDFS-15630 RBF: Fix wrong client IP info in CallerContext when requests mount points with multi-destinations.
• is blocked by: HADOOP-17276 Extend CallerContext to make it include many items
• is duplicated by: HADOOP-16254 Add proxy address in IPC connection
• is related to: HDFS-13248 RBF: Namenode need to choose block location for the client
• relates to: HDFS-13365 RBF: Adding trace support
• links to: GitHub Pull Request #2363