[ 
https://issues.apache.org/jira/browse/HDFS-16624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

fanshilun updated HDFS-16624:
-----------------------------
    Description: 
HDFS-16619 found an error message during Junit unit testing, as follows:

expected:<[SUCCESS: Changed property dfs.datanode.peer.stats.enabled]> but 
was:<[ From: "false"]>

After code debugging, it was found that there was an error in the selection 
outs.get(2) of the assertion(1208), index should be equal to 1.

Please refer to the attachment for debugging pictures

!testAllDatanodesReconfig.png!

  was:
HDFS-16619 found an error message during Junit unit testing, as follows:

expected:<[SUCCESS: Changed property dfs.datanode.peer.stats.enabled]> but 
was:<[ From: "false"]>

After code debugging, it was found that there was an error in the selection 
outs.get(x) of the assertion.

Please refer to the attachment for debugging pictures

!testAllDatanodesReconfig.png!


> Fix org.apache.hadoop.hdfs.tools.TestDFSAdmin#testAllDatanodesReconfig ERROR
> ----------------------------------------------------------------------------
>
>                 Key: HDFS-16624
>                 URL: https://issues.apache.org/jira/browse/HDFS-16624
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 3.4.0
>            Reporter: fanshilun
>            Assignee: fanshilun
>            Priority: Major
>         Attachments: testAllDatanodesReconfig.png
>
>
> HDFS-16619 found an error message during Junit unit testing, as follows:
> expected:<[SUCCESS: Changed property dfs.datanode.peer.stats.enabled]> but 
> was:<[ From: "false"]>
> After code debugging, it was found that there was an error in the selection 
> outs.get(2) of the assertion(1208), index should be equal to 1.
> Please refer to the attachment for debugging pictures
> !testAllDatanodesReconfig.png!



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to