Skip to content

Conversation

@gmarouli
Copy link
Contributor

In this PR we add support for the failure store for system data streams. Specifically:

  • We pass the system descriptor so the failure index can be created based on that.
  • We extend the tests to ensure it works
  • We remove a guard we had but I wasn't able to test it because it only gets triggered if the data stream gets created right after a failure in the ingest pipeline, and I didn't see how to add one (yet).
  • We extend the system data stream migration to ensure this is also working.

@gmarouli gmarouli added >non-issue :Core/Infra/Core Core issues without another label :Data Management/Data streams Data streams and their lifecycles labels Apr 10, 2025
@gmarouli gmarouli requested a review from a team April 10, 2025 08:27
@elasticsearchmachine elasticsearchmachine added Team:Core/Infra Meta label for core/infra team Team:Data Management Meta label for data/management team v9.1.0 labels Apr 10, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

Copy link
Contributor

@alexey-ivanov-es alexey-ivanov-es left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've left a small comment, overall LGTM

}

List<Index> failureIndices = dataStream.getFailureIndices();
assertThat(failureIndices, hasSize(failureIndices.size()));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This assertion always passes, did you mean something else?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:face_palm: yes I will fix it. Thank you for pointing it out

@gmarouli gmarouli added auto-backport Automatically create backport pull requests when merged v8.19.0 auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) and removed auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) labels Apr 10, 2025
@elasticsearchmachine elasticsearchmachine merged commit 78ac5d5 into elastic:main Apr 10, 2025
17 checks passed
@gmarouli gmarouli deleted the failure-store/system-indices branch April 10, 2025 19:14
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.x Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 126585

@gmarouli
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.x

Questions ?

Please refer to the Backport tool documentation

gmarouli added a commit to gmarouli/elasticsearch that referenced this pull request Apr 10, 2025
…c#126585)

In this PR we add support for the failure store for system data streams.
Specifically:

- We pass the system descriptor so the failure index can be created based on that.
- We extend the tests to ensure it works
- We remove a guard we had but I wasn't able to test it because it only gets triggered if the data stream gets created right after a failure in the ingest pipeline, and I didn't see how to add one (yet).
- We extend the system data stream migration to ensure this is also working.

(cherry picked from commit 78ac5d5)

# Conflicts:
#	x-pack/plugin/security/src/internalClusterTest/java/org/elasticsearch/integration/DataStreamLifecycleServiceRuntimeSecurityIT.java
gmarouli added a commit that referenced this pull request Apr 11, 2025
… (#126639)

In this PR we add support for the failure store for system data streams.
Specifically:

- We pass the system descriptor so the failure index can be created based on that.
- We extend the tests to ensure it works
- We remove a guard we had but I wasn't able to test it because it only gets triggered if the data stream gets created right after a failure in the ingest pipeline, and I didn't see how to add one (yet).
- We extend the system data stream migration to ensure this is also working.

(cherry picked from commit 78ac5d5)

# Conflicts:
#	x-pack/plugin/security/src/internalClusterTest/java/org/elasticsearch/integration/DataStreamLifecycleServiceRuntimeSecurityIT.java
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) :Core/Infra/Core Core issues without another label :Data Management/Data streams Data streams and their lifecycles >non-issue Team:Core/Infra Meta label for core/infra team Team:Data Management Meta label for data/management team v8.19.0 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants