[
https://issues.apache.org/jira/browse/HDFS-16611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fanshilun updated HDFS-16611:
-----------------------------
Description:
When I was dealing with HDFS-16590 JIRA, Junit Tests often reported errors, I
found that the following error messages often appear
org.apache.hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes#
testCircularLinkedListWrites
This method runs very close to success. It can be found that the current item
is approximately equal to the target length in 3 runs. I think it can reduce
the length of LIST_LENGTH and prolong the RUNTIME time, which can effectively
increase the success rate of this Test.
Reducing LIST_LENGTH does not change the running purpose of Test, and it can
also test Circular Writes in the case of NN failover.
* 1st run
{code:java}
1st run
[ERROR]
testCircularLinkedListWrites(org.apache.hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes)
Time elapsed: 114.252 s <<< FAILURE!
java.lang.AssertionError:
Some writers didn't complete in expected runtime! Current writer
state:[Circular Writer:
directory: /test-0
target length: 50
current item: 43
done: false
, Circular Writer:
directory: /test-1
target length: 50
current item: 47
done: false
, Circular Writer:
directory: /test-2
target length: 50
current item: 42
done: false
] expected:<0> but was:<3>
{code}
* 2st run
{code:java}
[ERROR]
testCircularLinkedListWrites(org.apache.hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes)
Time elapsed: 110.349 s <<< FAILURE!
java.lang.AssertionError:
Some writers didn't complete in expected runtime! Current writer
state:[Circular Writer:
directory: /test-0
target length: 50
current item: 50
done: false
, Circular Writer:
directory: /test-1
target length: 50
current item: 49
done: false
, Circular Writer:
directory: /test-2
target length: 50
current item: 49
done: false
] expected:<0> but was:<3>
{code}
* 3rd run
{code:java}
[ERROR]
testCircularLinkedListWrites(org.apache.hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes)
Time elapsed: 109.364 s <<< FAILURE!
java.lang.AssertionError:
Some writers didn't complete in expected runtime! Current writer
state:[Circular Writer:
directory: /test-0
target length: 50
current item: 47
done: false
, Circular Writer:
directory: /test-1
target length: 50
current item: 47
done: false
, Circular Writer:
directory: /test-2
target length: 50
current item: 46
done: false
] expected:<0> but was:<3>
{code}
was:
When I was dealing with HDFS-16590 JIRA, Junit Tests often reported errors, I
found that the following error messages often appear
org.apache.hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes#
testCircularLinkedListWrites
This method runs very close to success. It can be found that the current item
is approximately equal to the target length in 3 runs. I think it can reduce
the length of LIST_LENGTH and prolong the RUNTIME time, which can effectively
increase the success rate of this Test.
Reducing LIST_LENGTH does not change the running purpose of Text, and it can
also test Circular Writes in the case of NN failover.
* 1st run
{code:java}
1st run
[ERROR]
testCircularLinkedListWrites(org.apache.hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes)
Time elapsed: 114.252 s <<< FAILURE!
java.lang.AssertionError:
Some writers didn't complete in expected runtime! Current writer
state:[Circular Writer:
directory: /test-0
target length: 50
current item: 43
done: false
, Circular Writer:
directory: /test-1
target length: 50
current item: 47
done: false
, Circular Writer:
directory: /test-2
target length: 50
current item: 42
done: false
] expected:<0> but was:<3>
{code}
* 2st run
{code:java}
[ERROR]
testCircularLinkedListWrites(org.apache.hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes)
Time elapsed: 110.349 s <<< FAILURE!
java.lang.AssertionError:
Some writers didn't complete in expected runtime! Current writer
state:[Circular Writer:
directory: /test-0
target length: 50
current item: 50
done: false
, Circular Writer:
directory: /test-1
target length: 50
current item: 49
done: false
, Circular Writer:
directory: /test-2
target length: 50
current item: 49
done: false
] expected:<0> but was:<3>
{code}
* 3rd run
{code:java}
[ERROR]
testCircularLinkedListWrites(org.apache.hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes)
Time elapsed: 109.364 s <<< FAILURE!
java.lang.AssertionError:
Some writers didn't complete in expected runtime! Current writer
state:[Circular Writer:
directory: /test-0
target length: 50
current item: 47
done: false
, Circular Writer:
directory: /test-1
target length: 50
current item: 47
done: false
, Circular Writer:
directory: /test-2
target length: 50
current item: 46
done: false
] expected:<0> but was:<3>
{code}
> impove TestSeveralNameNodes#testCircularLinkedListWrites Params
> ---------------------------------------------------------------
>
> Key: HDFS-16611
> URL: https://issues.apache.org/jira/browse/HDFS-16611
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Affects Versions: 3.4.0
> Reporter: fanshilun
> Assignee: fanshilun
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When I was dealing with HDFS-16590 JIRA, Junit Tests often reported errors,
> I found that the following error messages often appear
> org.apache.hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes#
> testCircularLinkedListWrites
> This method runs very close to success. It can be found that the current item
> is approximately equal to the target length in 3 runs. I think it can reduce
> the length of LIST_LENGTH and prolong the RUNTIME time, which can effectively
> increase the success rate of this Test.
> Reducing LIST_LENGTH does not change the running purpose of Test, and it can
> also test Circular Writes in the case of NN failover.
> * 1st run
> {code:java}
> 1st run
> [ERROR]
> testCircularLinkedListWrites(org.apache.hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes)
> Time elapsed: 114.252 s <<< FAILURE!
> java.lang.AssertionError:
> Some writers didn't complete in expected runtime! Current writer
> state:[Circular Writer:
> directory: /test-0
> target length: 50
> current item: 43
> done: false
> , Circular Writer:
> directory: /test-1
> target length: 50
> current item: 47
> done: false
> , Circular Writer:
> directory: /test-2
> target length: 50
> current item: 42
> done: false
> ] expected:<0> but was:<3>
> {code}
> * 2st run
> {code:java}
> [ERROR]
> testCircularLinkedListWrites(org.apache.hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes)
> Time elapsed: 110.349 s <<< FAILURE!
> java.lang.AssertionError:
> Some writers didn't complete in expected runtime! Current writer
> state:[Circular Writer:
> directory: /test-0
> target length: 50
> current item: 50
> done: false
> , Circular Writer:
> directory: /test-1
> target length: 50
> current item: 49
> done: false
> , Circular Writer:
> directory: /test-2
> target length: 50
> current item: 49
> done: false
> ] expected:<0> but was:<3>
> {code}
> * 3rd run
> {code:java}
> [ERROR]
> testCircularLinkedListWrites(org.apache.hadoop.hdfs.server.namenode.ha.TestSeveralNameNodes)
> Time elapsed: 109.364 s <<< FAILURE!
> java.lang.AssertionError:
> Some writers didn't complete in expected runtime! Current writer
> state:[Circular Writer:
> directory: /test-0
> target length: 50
> current item: 47
> done: false
> , Circular Writer:
> directory: /test-1
> target length: 50
> current item: 47
> done: false
> , Circular Writer:
> directory: /test-2
> target length: 50
> current item: 46
> done: false
> ] expected:<0> but was:<3>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
