[
https://issues.apache.org/jira/browse/HDFS-16700?focusedWorklogId=796414&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-796414
]
ASF GitHub Bot logged work on HDFS-16700:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Jul/22 14:57
Start Date: 29/Jul/22 14:57
Worklog Time Spent: 10m
Work Description: jianghuazhu opened a new pull request, #4659:
URL: https://github.com/apache/hadoop/pull/4659
### Description of PR
When applying RBF, the ip recorded in the log file saved in the NameNode is
still the Router. The real client ip should be logged.
Details: HDFS-16700
### How was this patch tested?
When hadoop.caller.context.enabled=true, you should see the client ip
recorded in the NameNode log file.
Issue Time Tracking
-------------------
Worklog Id: (was: 796414)
Remaining Estimate: 0h
Time Spent: 10m
> Record the real client ip carried by the Router in the NameNode log
> -------------------------------------------------------------------
>
> Key: HDFS-16700
> URL: https://issues.apache.org/jira/browse/HDFS-16700
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode, rbf
> Affects Versions: 3.3.3
> Reporter: JiangHua Zhu
> Assignee: JiangHua Zhu
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Here are some logs recorded by the NameNode when using RBF:
> {code:java}
> 2022-07-28 19:31:07,126 INFO ipc.Server: IPC Server handler 8 on default port
> 8020, call Call#127 Retry#0
> org.apache.hadoop.hdfs.protocol.ClientProtocol.getFileInfo from
> 172.10.100.67:58001
> {code}
> The ip information here is still the router. If the real client ip is
> recorded, it will more clearly express where the request comes from.
> E.g:
> {code:java}
> 2022-07-29 19:31:07,126 INFO ipc.Server: IPC Server handler 8 on default port
> 8020, call Call#127 Retry#0
> org.apache.hadoop.hdfs.protocol.ClientProtocol.getFileInfo from
> 172.10.100.67:58001, client=172.111.65.123:43232
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
