hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chen Zhang (Jira)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-14775) Add Timestamp for longest FSN write/read lock held log
Date Mon, 26 Aug 2019 15:59:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-14775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915906#comment-16915906

Chen Zhang commented on HDFS-14775:

Upload patch v2 to fix checkstyle error, and all the failed test can pass in local. It's curious
that so many tests failed on Jenkins.

> Add Timestamp for longest FSN write/read lock held log
> ------------------------------------------------------
>                 Key: HDFS-14775
>                 URL: https://issues.apache.org/jira/browse/HDFS-14775
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Chen Zhang
>            Assignee: Chen Zhang
>            Priority: Major
>         Attachments: HDFS-14775.001.patch, HDFS-14775.002.patch
> HDFS-13946 improved the log for longest read/write lock held time, it's very useful improvement.
> In some condition, we need to locate the detailed call information(user, ip, path, etc.)
for longest lock holder, but the default throttle interval(10s) is too long to find the corresponding
audit log. I think we should add the timestamp for the {{longestWriteLockHeldStackTrace}}

This message was sent by Atlassian Jira

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message