hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Krogen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10817) Add Logging for Long-held NN Read Locks
Date Thu, 01 Sep 2016 00:32:20 GMT

     [ https://issues.apache.org/jira/browse/HDFS-10817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Erik Krogen updated HDFS-10817:
-------------------------------
    Attachment: HDFS-10817.addendum.000.patch

Discovered that the test fails on branch-2 because the logs do not include the thread name,
which the test was using to determine which log statements came from which threads. The test
has been modified to use a different technique to determine this. 

> Add Logging for Long-held NN Read Locks
> ---------------------------------------
>
>                 Key: HDFS-10817
>                 URL: https://issues.apache.org/jira/browse/HDFS-10817
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: logging, namenode
>            Reporter: Erik Krogen
>            Assignee: Erik Krogen
>         Attachments: HDFS-10817.000.patch, HDFS-10817.001.patch, HDFS-10817.002.patch,
HDFS-10817.003.patch, HDFS-10817.004.patch, HDFS-10817.addendum.000.patch
>
>
> Right now the Namenode will log when a write lock is held for a long time to help tracks
methods which are causing expensive delays. Let's do the same for read locks since these operations
may also be expensive/long and cause delays. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message