[
https://issues.apache.org/jira/browse/HDFS-10817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453863#comment-15453863
]
Erik Krogen edited comment on HDFS-10817 at 9/1/16 12:32 AM:
-------------------------------------------------------------
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. See addendum patch.
was (Author: xkrogen):
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: [email protected]
For additional commands, e-mail: [email protected]
