Thanks Ayush for bringing this up.
NameNode uses clientId and callId for retry cache.
- clientId: I'm +1 for adding remoteAddr in IPCConectionContext and NN
should use remoteAddr for clientId. This also resolves data locality issue.
- callId: Can DFSRouters share the callId and the clientId of the
Ayush, Thanks for bringing this up, it is very meaningful!
Add one more typical problem, NameNode should log both real client and
Router 's ip. But now NN just logs router's ip, it's difficult for
troubleshooting
Ayush Saxena 于2020年5月4日周一 下午5:26写道：
> Hi All,
> Wanted to share and discuss a pr
Hi Ayush,
Thank you for summary and re-launching this discussion. Both of JIRA's
links are very helpful for pushing it forward.
I would like to underline that this is a serious issue and very hope that
we could get the solution here. As far as know, there are many users who
deploy RBF meet this is
Hi All,
Wanted to share and discuss a problem that we are facing in the present
situation when using Router Based Federation. Presently when a client
connects through Router to Namenode, the Namenode receives the caller
context of the router rather than being of the actual client. This
typically ca
