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
RBF: Namenode need to choose block location for the client
RBF: Adding trace support
GitHub Pull Request #2363