[
https://issues.apache.org/jira/browse/HDFS-16266?focusedWorklogId=663255&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-663255
]
ASF GitHub Bot logged work on HDFS-16266:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Oct/21 14:23
Start Date: 10/Oct/21 14:23
Worklog Time Spent: 10m
Work Description: tomscut opened a new pull request #3538:
URL: https://github.com/apache/hadoop/pull/3538
JIRA: [HDFS-16266](https://issues.apache.org/jira/browse/HDFS-16266)
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.
Before:
After:
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 663255)
Remaining Estimate: 0h
Time Spent: 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
> Time Spent: 10m
> 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: [email protected]
For additional commands, e-mail: [email protected]
