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-10896) Move lock logging logic from FSNamesystem into FSNamesystemLock
Date Mon, 26 Sep 2016 21:35:22 GMT

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

Erik Krogen updated HDFS-10896:
    Attachment: HDFS-10896.001.patch

Rebased for patch v001.

> Move lock logging logic from FSNamesystem into FSNamesystemLock
> ---------------------------------------------------------------
>                 Key: HDFS-10896
>                 URL: https://issues.apache.org/jira/browse/HDFS-10896
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Erik Krogen
>            Assignee: Erik Krogen
>              Labels: logging, namenode
>         Attachments: HDFS-10896.000.patch, HDFS-10896.001.patch
> There are a number of tickets (HDFS-10742, HDFS-10817, HDFS-10713, this subtask's story
HDFS-10475) which are adding/improving logging/metrics around the {{FSNamesystemLock}}. All
of this is done in {{FSNamesystem}} right now, which is polluting the namesystem with ThreadLocal
variables, timing counters, etc. which are only relevant to the lock itself and the number
of these increases as the logging/metrics become more sophisticated. It would be best to move
these all into FSNamesystemLock to keep the metrics/logging tied directly to the item of interest.

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