[
https://issues.apache.org/jira/browse/HDFS-15095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013153#comment-17013153
]
Hudson commented on HDFS-15095:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17847 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/17847/])
HDFS-15095. Fix TestDecommissioningStatus. Contributed by Ahmed Hussein.
(kihwal: rev 5fb901ac4017b4f13b089ecd920e864cd53ad3a6)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestDecommissioningStatus.java
> Fix accidental comment in flaky test TestDecommissioningStatus
> --------------------------------------------------------------
>
> Key: HDFS-15095
> URL: https://issues.apache.org/jira/browse/HDFS-15095
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Reporter: Ahmed Hussein
> Assignee: Ahmed Hussein
> Priority: Major
> Fix For: 3.3.0, 3.1.4, 3.2.2
>
> Attachments: HDFS-15095.001.patch, HDFS-15095.002.patch
>
>
> There are some old Jiras suggesting that "{{testDecommissionStatus"}} is
> flaky.
> * HDFS-12188
> * HDFS-9599
> * HDFS-9950
> * HDFS-10755
> However, HDFS-14854 fix accidentally commented out one of the checks in
> {{TestDecommissioningStatus.testDecommissionStatus()"}}. This Jira will
> restore the commented out code and adds a blocking queue to make the test
> case deterministic.
> My intuition is that monitor task launched by AdminManager may not have
> enough time to act before we start verifying the status. I suggest the force
> the main thread to block until the node is added to the blocked node.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
