Skip to content

[CI] CCR - testValidateFollowingIndexSettings fails #33379

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

Closed
dnhatn opened this issue Sep 4, 2018 · 4 comments
Closed

[CI] CCR - testValidateFollowingIndexSettings fails #33379

dnhatn opened this issue Sep 4, 2018 · 4 comments
Labels
:Distributed Indexing/CCR Issues around the Cross Cluster State Replication features >test-failure Triaged test failures from CI

Comments

@dnhatn
Copy link
Member

dnhatn commented Sep 4, 2018

I have not looked into the failure. I open this issue so that we can mute the test.

CI: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-unix-compatibility/os=sles/2651/console

Log: validate_follow_setting.txt.zip

Reproduce command:

./gradlew :x-pack:plugin:ccr:internalClusterTest \
  -Dtests.seed=7E4E234E7384C59F \
  -Dtests.class=org.elasticsearch.xpack.ccr.ShardChangesIT \
  -Dtests.method="testValidateFollowingIndexSettings" \
  -Dtests.security.manager=true \
  -Dtests.locale=id \
  -Dtests.timezone=Australia/Lindeman \
  -Dcompiler.java=10 \
  -Druntime.java=8
@dnhatn dnhatn added >test-failure Triaged test failures from CI :Distributed Indexing/CCR Issues around the Cross Cluster State Replication features labels Sep 4, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

dnhatn added a commit that referenced this issue Sep 4, 2018
dnhatn added a commit that referenced this issue Sep 4, 2018
@martijnvg
Copy link
Member

@dnhatn I'm removing this test in #33367 as it is no longer possible to use the follow api without the create_and_follow api creating the follow index (this api adds custom index metadata).

Also I think that this should be tested in a unit test only and that already has been done in FollowIndexActionTests.

@martijnvg
Copy link
Member

I think the reason that this test failed is because not all leader shard copies were ready and the test does not wait for all leader shard copies to be ready before executing the follow api.

 2.29s J1 | ShardChangesIT.testValidateFollowingIndexSettings <<< FAILURES!
   > Throwable #1: java.lang.IllegalArgumentException: Not all copies of follow shard are started
   >    at org.elasticsearch.xpack.ccr.action.ShardFollowTasksExecutor.validate(ShardFollowTasksExecutor.java:77)
   >    at org.elasticsearch.xpack.ccr.action.ShardFollowTasksExecutor.validate(ShardFollowTasksExecutor.java:53)
   >    at org.elasticsearch.persistent.PersistentTasksClusterService$1.execute(PersistentTasksClusterService.java:77)
   >    at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:45)
   >    at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:639)
   >    at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:268)
   >    at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:198)
   >    at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:133)
   >    at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:150)
   >    at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:188)
   >    at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:624)
   >    at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:244)
   >    at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:207)
   >    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
   >    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

@martijnvg
Copy link
Member

This test no longer exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Indexing/CCR Issues around the Cross Cluster State Replication features >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

3 participants