hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhe Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9145) Tracking methods that hold FSNamesytemLock for too long
Date Tue, 30 Aug 2016 19:13:20 GMT

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

Zhe Zhang commented on HDFS-9145:

Thanks [~kihwal] for noticing this. But are we still using CHANGES.txt to keep track of branch-2.7
changes? This JIRA is a special case because when it went in branch-2 it had a CHANGES.txt
entry. But for all new JIRAs targeting 2.7.4 we are no longer putting in CHANGES.txt entries

> Tracking methods that hold FSNamesytemLock for too long
> -------------------------------------------------------
>                 Key: HDFS-9145
>                 URL: https://issues.apache.org/jira/browse/HDFS-9145
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Jing Zhao
>            Assignee: Mingliang Liu
>             Fix For: 2.8.0, 2.7.4, 3.0.0-alpha1
>         Attachments: HDFS-9145.000.patch, HDFS-9145.001.patch, HDFS-9145.002.patch, HDFS-9145.003.patch,
> It will be helpful that if we can have a way to track (or at least log a msg) if some
operation is holding the FSNamesystem lock for a long time.

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