[
https://issues.apache.org/jira/browse/HDFS-15423?focusedWorklogId=534501&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-534501
]
ASF GitHub Bot logged work on HDFS-15423:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Jan/21 19:58
Start Date: 11/Jan/21 19:58
Worklog Time Spent: 10m
Work Description: goiri commented on pull request #2605:
URL: https://github.com/apache/hadoop/pull/2605#issuecomment-758187791
> @goiri Thanks for the further review.
> I found these TestRouterWebHdfsContractXX are flaky with my change and I
think they are related with the fact that for the MiniRouterDFSCluster these
tests created (in RouterWebHDFSContract), datanodes are shared among
nameservices. The datanode report would be sometimes overwritten as :
ns0->/ns0/rack would be overwritten by ns1->/ns1/rack for the same dn.
Therefore for some tests we saw that no available datanode was found.
> Do you think we should fix it first? If so should it be in a separate
patch? Thanks!
Adding flaky tests is not a good idea.
Let's try to fix it in this PR.
----------------------------------------------------------------
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: 534501)
Time Spent: 1h 40m (was: 1.5h)
> RBF: WebHDFS create shouldn't choose DN from all sub-clusters
> -------------------------------------------------------------
>
> Key: HDFS-15423
> URL: https://issues.apache.org/jira/browse/HDFS-15423
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: rbf, webhdfs
> Reporter: Chao Sun
> Assignee: Fengnan Li
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> In {{RouterWebHdfsMethods}} and for a {{CREATE}} call, {{chooseDatanode}}
> first gets all DNs via {{getDatanodeReport}}, and then randomly pick one from
> the list via {{getRandomDatanode}}. This logic doesn't seem correct as it
> should pick a DN for the specific cluster(s) of the input {{path}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
