Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[CI] SimpleClusterStateIT testMetadataVersion failed #37820

Closed
droberts195 opened this issue Jan 24, 2019 · 5 comments
Closed

[CI] SimpleClusterStateIT testMetadataVersion failed #37820

droberts195 opened this issue Jan 24, 2019 · 5 comments
Assignees
@dnhatn
Labels
:Distributed Coordination/Cluster Coordination Cluster formation and cluster state publication, including cluster membership and fault detection. >test-failure Triaged test failures from CI

Comments

@droberts195
Copy link
Contributor

SimpleClusterStateIT testMetadataVersion failed in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+intake/1151/console

The error was:

12:29:14 FAILURE 0.66s J5 | SimpleClusterStateIT.testMetadataVersion <<< FAILURES!
12:29:14    > Throwable #1: java.lang.AssertionError: 
12:29:14    > Expected: <81L>
12:29:14    >      but: was <82L>
12:29:14    > 	at __randomizedtesting.SeedInfo.seed([1E57DA32C36FCB37:F1520789EF481A64]:0)
12:29:14    > 	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
12:29:14    > 	at org.elasticsearch.cluster.SimpleClusterStateIT.testMetadataVersion(SimpleClusterStateIT.java:126)
12:29:14    > 	at java.lang.Thread.run(Thread.java:748)

This did not reproduce for me locally using:

./gradlew :server:integTest \
  -Dtests.seed=1E57DA32C36FCB37 \
  -Dtests.class=org.elasticsearch.cluster.SimpleClusterStateIT \
  -Dtests.method="testMetadataVersion" \
  -Dtests.security.manager=true \
  -Dtests.locale=sr-Latn-ME \
  -Dtests.timezone=NZ \
  -Dcompiler.java=11 \
  -Druntime.java=8
@droberts195 droberts195 added >test-failure Triaged test failures from CI :Distributed Coordination/Cluster Coordination Cluster formation and cluster state publication, including cluster membership and fault detection. labels Jan 24, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

droberts195 added a commit that referenced this issue Jan 24, 2019
@droberts195
Mute SimpleClusterStateIT testMetadataVersion
1c37304 
Due to #37820
@droberts195
Copy link
Contributor Author

The test has been muted in 6.x in 1c37304

@droberts195
Copy link
Contributor Author

A very similar error occurred in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+intake/1149/consoleText:

FAILURE 0.86s J5 | SimpleClusterStateIT.testMetadataVersion <<< FAILURES!
   > Throwable #1: java.lang.AssertionError: 
   > Expected: <84L>
   >      but: was <85L>
   > 	at __randomizedtesting.SeedInfo.seed([C69507D5DD461A67:2990DA6EF161CB34]:0)
   > 	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
   > 	at org.elasticsearch.cluster.SimpleClusterStateIT.testMetadataVersion(SimpleClusterStateIT.java:122)
   > 	at java.lang.Thread.run(Thread.java:748)

@dnhatn dnhatn self-assigned this Jan 24, 2019
@dnhatn
Copy link
Member

dnhatn commented Jan 24, 2019

I am on it now.

@cbuescher cbuescher mentioned this issue Jan 24, 2019
Closed
@droberts195
Copy link
Contributor Author

This has just failed on master too, in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=java11,ES_RUNTIME_JAVA=java11,nodes=virtual&&linux/200/console:

16:37:08 FAILURE 3.05s J4 | SimpleClusterStateIT.testMetadataVersion <<< FAILURES!
16:37:08    > Throwable #1: java.lang.AssertionError: 
16:37:08    > Expected: <361L>
16:37:08    >      but: was <362L>
16:37:08    > 	at __randomizedtesting.SeedInfo.seed([63FD97398FF731EE:8CF84A82A3D0E0BD]:0)
16:37:08    > 	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
16:37:08    > 	at org.elasticsearch.cluster.SimpleClusterStateIT.testMetadataVersion(SimpleClusterStateIT.java:133)
16:37:08    > 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
16:37:08    > 	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
16:37:08    > 	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
16:37:08    > 	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
16:37:08    > 	at java.base/java.lang.Thread.run(Thread.java:834)

The repro command was:

./gradlew :server:integTest \
  -Dtests.seed=63FD97398FF731EE \
  -Dtests.class=org.elasticsearch.cluster.SimpleClusterStateIT \
  -Dtests.method="testMetadataVersion" \
  -Dtests.security.manager=true \
  -Dtests.locale=en-SS \
  -Dtests.timezone=Europe/Andorra \
  -Dcompiler.java=11 \
  -Druntime.java=11

I muted the test in master too in 0e36adc

@droberts195 droberts195 changed the title [CI] SimpleClusterStateIT testMetadataVersion failed in 6.x [CI] SimpleClusterStateIT testMetadataVersion failed Jan 24, 2019
droberts195 added a commit that referenced this issue Jan 24, 2019
@droberts195
Mute SimpleClusterStateIT testMetadataVersion
0e36adc 
Due to #37820
dnhatn added a commit to dnhatn/elasticsearch that referenced this issue Jan 24, 2019
@dnhatn
Relax cluster metadata version check
3ae4a71 
If the in_sync_allocations of index-1 or index-2 is changed, the
metadata version will be increased. This leads to the failure in
the metadata version checks. We need to relax them.

Closes elastic#37820
@dnhatn dnhatn mentioned this issue Jan 24, 2019
Merged
dnhatn added a commit that referenced this issue Jan 25, 2019
@dnhatn
Relax cluster metadata version check (#37834)
5cd4dfb 
If the in_sync_allocations of index-1 or index-2 is changed, the
metadata version will be increased. This leads to the failure in
the metadata version checks. We need to relax them.

Closes #37820
dnhatn added a commit that referenced this issue Jan 25, 2019
@dnhatn
Relax cluster metadata version check (#37834)
7defbf3 
If the in_sync_allocations of index-1 or index-2 is changed, the
metadata version will be increased. This leads to the failure in
the metadata version checks. We need to relax them.

Closes #37820
dnhatn added a commit that referenced this issue Jan 26, 2019
@dnhatn
Relax cluster metadata version check (#37834)
1f6a8b3 
If the in_sync_allocations of index-1 or index-2 is changed, the
metadata version will be increased. This leads to the failure in
the metadata version checks. We need to relax them.

Closes #37820
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dnhatn dnhatn

Labels
:Distributed Coordination/Cluster Coordination Cluster formation and cluster state publication, including cluster membership and fault detection. >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@droberts195 @dnhatn @elasticmachine