Description
There are two issues about client IP info in CallerContext when we try to request mount points with multi-destinations.
- the clientIp would duplicate in CallerContext when RouterRpcClient#invokeSequential.
- the clientIp would miss in CallerContext when RouterRpcClient#invokeConcurrent.
Attachments
Attachments
Issue Links
- is broken by
-
HDFS-13293 RBF: The RouterRPCServer should transfer client IP via CallerContext to NamenodeRpcServer
- Resolved