-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[Transform] Prevent stopping of transforms due to threadpool limitation #81912
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
[Transform] Prevent stopping of transforms due to threadpool limitation #81912
Conversation
… the indexer threadpool was only used on start. fixes elastic#81796
|
Pinging @elastic/ml-core (Team:ML) |
przemekwitek
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| @Override | ||
| public boolean maybeTriggerAsyncJob(long now) { | ||
| boolean triggered; | ||
| // threadpool: trigger_engine_scheduler if triggered from the scheduler |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the alternative (if not triggered from the scheduler)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is also called by the transform task when it starts, e.g. as a result of _start or if the transform re-initializes due to a task re-location (failover or upgrade).
|
@elasticmachine update branch |
|
@elasticmachine update branch |
…on (elastic#81912) remove the indexer threadpool and use the generic threadpool instead(The indexer threadpool was only used on start) fixes elastic#81796
remove the indexer threadpool and use the generic threadpool instead(The indexer threadpool was only used on start)
fixes #81796