hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12349) Improve log message when it could not alloc enough blocks for EC
Date Fri, 15 Sep 2017 18:53:00 GMT

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

Andrew Wang commented on HDFS-12349:
------------------------------------

+1 LGTM. Could you also file a JIRA to add a JUnit timeout to TestBlockStatsMXBean? Right
now it's failing due to the surefire timeout which makes it much harder to debug.

> Improve log message when it could not alloc enough blocks for EC 
> -----------------------------------------------------------------
>
>                 Key: HDFS-12349
>                 URL: https://issues.apache.org/jira/browse/HDFS-12349
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: erasure-coding
>    Affects Versions: 3.0.0-alpha3
>            Reporter: Lei (Eddy) Xu
>            Assignee: Lei (Eddy) Xu
>            Priority: Minor
>             Fix For: 3.0.0-beta1
>
>         Attachments: HDFS-12349.00.patch, HDFS-12349.01.patch, HDFS-12349.02.patch, HDFS-12349.03.patch,
HDFS-12349.04.patch
>
>
> When an EC output stream could not alloc enough blocks for parity blocks, it sets the
warning.
> {code}
> if (blocks[i] == null) {
>         LOG.warn("Failed to get block location for parity block, index=" + i);
> {code}
> We should clarify the cause of this warning message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
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