[
https://issues.apache.org/jira/browse/HDFS-16266?focusedWorklogId=668307&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-668307
]
ASF GitHub Bot logged work on HDFS-16266:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Oct/21 11:26
Start Date: 21/Oct/21 11:26
Worklog Time Spent: 10m
Work Description: tomscut commented on pull request #3538:
URL: https://github.com/apache/hadoop/pull/3538#issuecomment-948516568
> Thanks for updating the PR, @tomscut.
>
> * I discussed with my colleagues, and they suggested that adding a new
port field would have less impact on users who are analyzing the audit logs
instead of expanding the existing IP field. What do you think?
> * After [HDFS-13293](https://issues.apache.org/jira/browse/HDFS-13293),
Router is forwarding client IP via CallerContext. How about adding the
client-side port to the CallerContext as well? Maybe we can consider it in
another JIRA.
Thanks @tasanuma and your colleagues for your good advice. And sorry for the
late reply.
```I discussed with my colleagues, and they suggested that adding a new port
field would have less impact on users who are analyzing the audit logs instead
of expanding the existing IP field. What do you think?```
I think it would be nice to put the port in a separate field, but adding the
port to the IP field is optional at the moment, so I'm a little confused which
way is more appropriate. I'd like to ask a few other committers to look at this
and give some suggestions. Anyway, I will update the PR in time.
@aajisaka @iwasakims @ayushtkn @ferhui @Hexiaoqiao @goiri @jojochuang Could
you please take a look at this and give some suggestions? Thank you very much!
```After [HDFS-13293](https://issues.apache.org/jira/browse/HDFS-13293),
Router is forwarding client IP via CallerContext. How about adding the
client-side port to the CallerContext as well? Maybe we can consider it in
another JIRA.```
I would like to open a new JIRA to do this. Thank you for pointing this out.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 668307)
Time Spent: 3h 20m (was: 3h 10m)
> Add remote port information to HDFS audit log
> ---------------------------------------------
>
> Key: HDFS-16266
> URL: https://issues.apache.org/jira/browse/HDFS-16266
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: tomscut
> Assignee: tomscut
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> In our production environment, we occasionally encounter a problem where a
> user submits an abnormal computation task, causing a sudden flood of
> requests, which causes the queueTime and processingTime of the Namenode to
> rise very high, causing a large backlog of tasks.
> We usually locate and kill specific Spark, Flink, or MapReduce tasks based on
> metrics and audit logs. Currently, IP and UGI are recorded in audit logs, but
> there is no port information, so it is difficult to locate specific processes
> sometimes. Therefore, I propose that we add the port information to the audit
> log, so that we can easily track the upstream process.
> Currently, some projects contain port information in audit logs, such as
> Hbase and Alluxio. I think it is also necessary to add port information for
> HDFS audit logs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
