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.

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

[CI] LegacyDynamicMappingIT testMappingsPropagatedToMasterNodeImmediatelyMultiType fails in 6.x #37817

Closed
droberts195 opened this issue Jan 24, 2019 · 5 comments
Assignees
Labels
:Search Foundations/Mapping Index mappings, including merging and defining field types >test-failure Triaged test failures from CI

Comments

@droberts195
Copy link
Contributor

LegacyDynamicMappingIT testMappingsPropagatedToMasterNodeImmediatelyMultiType failed in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+intake/1150/console

The error was:

12:20:09 ERROR   12.9s J2 | LegacyDynamicMappingIT.testMappingsPropagatedToMasterNodeImmediatelyMultiType <<< FAILURES!
12:20:09    > Throwable #1: java.lang.NullPointerException
12:20:09    > 	at __randomizedtesting.SeedInfo.seed([ED2233D5C1DA94DD:114FBFC798B4280]:0)
12:20:09    > 	at org.elasticsearch.index.mapper.LegacyDynamicMappingIT.testMappingsPropagatedToMasterNodeImmediatelyMultiType(LegacyDynamicMappingIT.java:56)
12:20:09    > 	at java.lang.Thread.run(Thread.java:748)

I tried to reproduce this locally using:

./gradlew :server:integTest \
  -Dtests.seed=ED2233D5C1DA94DD \
  -Dtests.class=org.elasticsearch.index.mapper.LegacyDynamicMappingIT \
  -Dtests.method="testMappingsPropagatedToMasterNodeImmediatelyMultiType" \
  -Dtests.security.manager=true \
  -Dtests.locale=en \
  -Dtests.timezone=Europe/Istanbul \
  -Dcompiler.java=11 \
  -Druntime.java=8

This time the test failed, but with a test assertion rather than an NPE:

FAILURE 6.68s | LegacyDynamicMappingIT.testMappingsPropagatedToMasterNodeImmediatelyMultiType <<< FAILURES!
   > Throwable #1: java.lang.AssertionError: Could not find [bar] in {_all={enabled=true}, properties={foo={type=long}}}
   >    at __randomizedtesting.SeedInfo.seed([ED2233D5C1DA94DD:114FBFC798B4280]:0)
   >    at org.elasticsearch.index.mapper.DynamicMappingIT.assertMappingsHaveField(DynamicMappingIT.java:66)
   >    at org.elasticsearch.index.mapper.LegacyDynamicMappingIT.testMappingsPropagatedToMasterNodeImmediatelyMultiType(LegacyDynamicMappingIT.java:51)
   >    at java.lang.Thread.run(Thread.java:745)
@droberts195 droberts195 added :Search Foundations/Mapping Index mappings, including merging and defining field types >test-failure Triaged test failures from CI labels Jan 24, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search

@droberts195
Copy link
Contributor Author

I muted this test for 6.x in bb5747c

@droberts195
Copy link
Contributor Author

The same test failed in https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+intake/1148/console

The exact failure is different to the two in the original issue description:

12:10:17 FAILURE 0.44s J2 | LegacyDynamicMappingIT.testMappingsPropagatedToMasterNodeImmediatelyMultiType <<< FAILURES!
12:10:17    > Throwable #1: java.lang.AssertionError
12:10:17    > 	at __randomizedtesting.SeedInfo.seed([C3ED4C523F85E2BF:2FDB847B87D434E2]:0)
12:10:17    > 	at org.elasticsearch.index.mapper.DynamicMappingIT.assertMappingsHaveField(DynamicMappingIT.java:61)
12:10:17    > 	at org.elasticsearch.index.mapper.LegacyDynamicMappingIT.testMappingsPropagatedToMasterNodeImmediatelyMultiType(LegacyDynamicMappingIT.java:46)
12:10:17    > 	at java.lang.Thread.run(Thread.java:748)

However, the sort of thing it's asserting is similar, so I've added it to this issue.

The repro line from this build was:

./gradlew :server:integTest \
  -Dtests.seed=C3ED4C523F85E2BF \
  -Dtests.class=org.elasticsearch.index.mapper.LegacyDynamicMappingIT \
  -Dtests.method="testMappingsPropagatedToMasterNodeImmediatelyMultiType" \
  -Dtests.security.manager=true \
  -Dtests.locale=id-ID \
  -Dtests.timezone=Asia/Saigon \
  -Dcompiler.java=11 \
  -Druntime.java=8

@cbuescher
Copy link
Member

Also @droberts195 mentioned he saw some general problems with cluster state related IT test today, namely #37820.
Not saying those are related but maybe worth keeping in mind since this seems to be a race condition, thus more difficult to reproduce.

@dnhatn dnhatn self-assigned this Jan 24, 2019
dnhatn added a commit that referenced this issue Jan 25, 2019
Dynamic mapping update of an index request no longer requires acks from
all nodes. We need busily to check the mapping update.

Relates #31140.
Closes #37817
@dnhatn
Copy link
Member

dnhatn commented Jan 25, 2019

I pushed f925690 to busily check the mapping update. This requires since #31140 where an index request no long requires acking on its dynamic mapping update. /cc @ywelsch.

@dnhatn dnhatn closed this as completed Jan 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Search Foundations/Mapping Index mappings, including merging and defining field types >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

4 participants