Skip to content

Conversation

@benwtrent
Copy link
Member

Timestats failures can cause issues for datafeeds in places other than stop. Example: Initial query/scroll. If persisting the search time fails, the datafeed treats that as a failure and stops.

We should continue executing through stats persistence failures and log if a failure occurs.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

Copy link

@droberts195 droberts195 left a comment

Choose a reason for hiding this comment

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

LGTM

@benwtrent benwtrent merged commit 197d5e7 into elastic:master Nov 22, 2019
@benwtrent benwtrent deleted the feature/ml-log-datafeed-timing-stats-failures branch November 22, 2019 17:39
benwtrent added a commit to benwtrent/elasticsearch that referenced this pull request Nov 22, 2019
Copy link
Contributor

@przemekwitek przemekwitek left a comment

Choose a reason for hiding this comment

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

LGTM

Thanks for fixing that, Ben!

@jpountz jpountz changed the title [ML] Stop timing stats failure propagation Stop timing stats failure propagation Dec 18, 2019
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.

5 participants