Skip to content

Conversation

@benwtrent
Copy link
Member

This exchanges the direct use of the Client for ResultsPersisterService. State doc persistence will now retry. Failures to persist state will still not throw, but will be audited and logged.

closes #50143

@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

Copy link
Member

@davidkyle davidkyle left a comment

Choose a reason for hiding this comment

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

LGTM

One nit is that ResultsPersisterService is a general class now used for state as well as results now, it doesn't know anything about anomaly detector results classes. Maybe it is just a PersistenceService or RetryPersistenceService

@benwtrent benwtrent merged commit 681e9fd into elastic:master Dec 13, 2019
@benwtrent benwtrent deleted the feature/ml-retry-state-bulk-indexing branch December 13, 2019 14:45
benwtrent added a commit to benwtrent/elasticsearch that referenced this pull request Dec 13, 2019
This exchanges the direct use of the `Client` for `ResultsPersisterService`. State doc persistence will now retry. Failures to persist state will still not throw, but will be audited and logged.
benwtrent added a commit that referenced this pull request Dec 13, 2019
This exchanges the direct use of the `Client` for `ResultsPersisterService`. State doc persistence will now retry. Failures to persist state will still not throw, but will be audited and logged.
@droberts195
Copy link

@dimitris-athanasiou in case you didn't notice, this PR also covers retries for indexing data frame analytics state, as the state is persisted by the same IndexingStateProcessor class. So I think it's just data frame updates for data frame analytics jobs that need retries adding now for complete cross-plugin consistency.

SivagurunathanV pushed a commit to SivagurunathanV/elasticsearch that referenced this pull request Jan 23, 2020
This exchanges the direct use of the `Client` for `ResultsPersisterService`. State doc persistence will now retry. Failures to persist state will still not throw, but will be audited and logged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[ML] Gracefully handle and retry state bulk indexing failures

5 participants