Repository navigation
[Transform] Wait while index is blocked - #119542
Merged
Merged
Conversation
When the destination index is blocked, the bulk request is ignored. Each subsequent trigger will check the cluster state if the index is unblocked or else drop the trigger. Users can call the ScheduleNow API to skip the index block check and let the trigger start the next checkpoint - if the index is blocked then the bulk request will fail again. While the Transform is skipping triggers, the state will display as `waiting` from the Get Stats API and on the Transform UI in Kibana.
Collaborator
|
Hi @prwhelan, I've created a changelog YAML for you. |
Member
Author
|
@elasticmachine update branch |
prwhelan
marked this pull request as ready for review
January 7, 2025 16:19
Collaborator
|
Pinging @elastic/ml-core (Team:ML) |
Member
Author
|
@elasticmachine update branch |
prwhelan
enabled auto-merge (squash)
January 8, 2025 21:25
prwhelan
added a commit
to prwhelan/elasticsearch
that referenced
this pull request
Jan 8, 2025
When the destination index is blocked, the bulk request is ignored. Each subsequent trigger will check the cluster state if the index is unblocked or else drop the trigger. Users can call the ScheduleNow API to skip the index block check and let the trigger start the next checkpoint - if the index is blocked then the bulk request will fail again. While the Transform is skipping triggers, the state will display as `waiting` from the Get Stats API and on the Transform UI in Kibana.
Collaborator
💚 Backport successful
|
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 8, 2025
When the destination index is blocked, the bulk request is ignored. Each subsequent trigger will check the cluster state if the index is unblocked or else drop the trigger. Users can call the ScheduleNow API to skip the index block check and let the trigger start the next checkpoint - if the index is blocked then the bulk request will fail again. While the Transform is skipping triggers, the state will display as `waiting` from the Get Stats API and on the Transform UI in Kibana.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the destination index is blocked, the bulk request is ignored. Each subsequent checkpoint will check the cluster state if the index is unblocked or else drop the checkpoint.
Users can call the ScheduleNow API to skip the index block check and let the Transform start the next checkpoint - if the index is blocked then the bulk request will fail again.
While the Transform is paused, the state will display as
waitingfrom the Get Stats API and on the Transform UI in Kibana.