hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8439) Adding more slow action log in critical read path
Date Thu, 21 May 2015 17:11:17 GMT

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

stack commented on HDFS-8439:

One last question [~liushaohui], sometimes you log at INFO level and other times WARN. Is
there a reason for that? If a mistake, I can fix on commit.

> Adding more slow action log in critical read path
> -------------------------------------------------
>                 Key: HDFS-8439
>                 URL: https://issues.apache.org/jira/browse/HDFS-8439
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Liu Shaohui
>            Assignee: Liu Shaohui
>            Priority: Minor
>         Attachments: HDFS-8439.001.patch, HDFS-8439.002.patch
> To dig a HBase read spike issue, we'd better to add more slow pread/seek log in read
flow to get the abnormal datanodes.
> Patch will be uploaded soon.

This message was sent by Atlassian JIRA

View raw message