Public signup for this instance is disabled. Go to our Self serve sign up page to request an account.
Share this issue
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
RBF: Integrate security changes with audit logging.
RBF: Fix wrong client IP info in CallerContext when requests mount points with multi-destinations.
Extend CallerContext to make it include many items
Add proxy address in IPC connection
RBF: Namenode need to choose block location for the client
RBF: Adding trace support
GitHub Pull Request #2363