[
https://issues.apache.org/jira/browse/HDFS-12349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161547#comment-16161547
]
Chris Douglas commented on HDFS-12349:
--------------------------------------
bq. Verified that all failed tests are not related
The failed tests are related. For example,
[TestSaslDataTransfer|https://builds.apache.org/job/PreCommit-HDFS-Build/21039/testReport/org.apache.hadoop.hdfs.protocol.datatransfer.sasl/TestSaslDataTransfer/testServerSaslNoClientSasl/]
{noformat}
Expected output to match /could only be replicated to 0 nodes/ but got:
File /file1 could only be written to 0 of the 1 minReplication. There are 1
datanode(s) running and 3 node(s) are excluded in this operation.
{noformat}
Please also fix the findbugs warning added in this patch.
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
