[
https://issues.apache.org/jira/browse/HDFS-15716?focusedWorklogId=521552&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-521552
]
ASF GitHub Bot logged work on HDFS-15716:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Dec/20 06:07
Start Date: 08/Dec/20 06:07
Worklog Time Spent: 10m
Work Description: iwasakims commented on pull request #2528:
URL: https://github.com/apache/hadoop/pull/2528#issuecomment-740400919
> On branch-2.10, this was fixed by waiting for the replication to be
complete.
Does this is done outside TestUpgradeDomainBlockPlacementPolicy? Your patch
looks applicable to branch-2.10 too. Since branch-2.10 still support Java 7,
cherry-picking would be easy by avoiding lambda here. I think the lambda does
not improve readability here. @amahussein
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 521552)
Time Spent: 40m (was: 0.5h)
> TestUpgradeDomainBlockPlacementPolicy flaky
> -------------------------------------------
>
> Key: HDFS-15716
> URL: https://issues.apache.org/jira/browse/HDFS-15716
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode, test
> Reporter: Ahmed Hussein
> Assignee: Ahmed Hussein
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In some slow runs {{TestUpgradeDomainBlockPlacementPolicy#testPlacement}} and
> {{TestUpgradeDomainBlockPlacementPolicy#testPlacementAfterDecommission}} fail.
> On branch-2.10, this was fixed by waiting for the replication to be complete.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
