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] FullClusterRestartSearchableSnapshotIndexCompatibilityIT testSearchableSnapshotUpgrade {p0=9.0.0} failing #119632

Closed
elasticsearchmachine opened this issue Jan 7, 2025 · 2 comments · Fixed by #119728
Assignees
Labels
:Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Indexing Meta label for Distributed Indexing team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Jan 7, 2025

Build Scans:

Reproduction Line:

./gradlew ":qa:lucene-index-compatibility:javaRestTest" --tests "org.elasticsearch.lucene.FullClusterRestartSearchableSnapshotIndexCompatibilityIT" -Dtests.method="testSearchableSnapshotUpgrade {p0=8.18.0}" -Dtests.seed=50782A34DAA4B322 -Dtests.locale=zh-Hant -Dtests.timezone=America/Ensenada -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.elasticsearch.client.ResponseException: method [PUT], host [http://[::1]:43855], URI [index-mounted-testsearchablesnapshotupgrade/_mappings], status line [HTTP/1.1 400 Bad Request]
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Limit of total fields [1] has been exceeded"}],"type":"illegal_argument_exception","reason":"Limit of total fields [1] has been exceeded"},"status":400}

Issue Reasons:

  • [main] 2 failures in test testSearchableSnapshotUpgrade {p0=9.0.0} (1.4% fail rate in 141 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine elasticsearchmachine added :Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. >test-failure Triaged test failures from CI labels Jan 7, 2025
elasticsearchmachine added a commit that referenced this issue Jan 7, 2025
…exCompatibilityIT testSearchableSnapshotUpgrade {p0=9.0.0} #119632
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test testSearchableSnapshotUpgrade {p0=9.0.0} (1.4% fail rate in 141 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Distributed Indexing Meta label for Distributed Indexing team labels Jan 7, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-distributed-indexing (Team:Distributed Indexing)

@tlrx tlrx self-assigned this Jan 7, 2025
@tlrx tlrx added the low-risk An open issue or test failure that is a low risk to future releases label Jan 7, 2025
@elasticsearchmachine elasticsearchmachine removed the needs:risk Requires assignment of a risk label (low, medium, blocker) label Jan 7, 2025
tlrx added a commit to tlrx/elasticsearch that referenced this issue Jan 8, 2025
It's stupid to pick a low value for `index.mapping.total_fields.limit`
when at the same time you also add random runtime fields => pick a value
large enough to avoid failing future random mapping updates.

Closes elastic#119646
Closes elastic#119632
Closes elastic#119631
@tlrx tlrx closed this as completed in 38260aa Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Indexing Meta label for Distributed Indexing team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants