hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-6529) Trace logging for RemoteBlockReader2 to identify remote datanode and file being read
Date Sat, 14 Jun 2014 00:58:06 GMT

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

Aaron T. Myers updated HDFS-6529:
---------------------------------

    Summary: Trace logging for RemoteBlockReader2 to identify remote datanode and file being
read  (was: Debug logging for RemoteBlockReader2 to identify remote datanode and file being
read)

> Trace logging for RemoteBlockReader2 to identify remote datanode and file being read
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-6529
>                 URL: https://issues.apache.org/jira/browse/HDFS-6529
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs-client
>    Affects Versions: 2.4.0
>            Reporter: Anubhav Dhoot
>            Assignee: Anubhav Dhoot
>            Priority: Minor
>         Attachments: HDFS-6529.patch
>
>
> The scenario is some download is stuck and we dont know which data node is the client
waiting and for which path.
> By turning this file trace logging we will get a running trace of which requests have
started and which have completed.
> If trace is not enabled, there is no overhead other than checking if trace is enabled



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message