You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MlDailyMaintenanceService is supposed to run in the ml_utility threadpool. We need to audit which thread each part of its work currently runs in, then ensure every stage actually does run in the ml_utility threadpool.
Additionally, there must be a flaw in the way MlDailyMaintenanceService is tested that means the assertions that actions don't run in network threads are not triggering.
The text was updated successfully, but these errors were encountered:
When ML is enabled the
MlDailyMaintenanceService
will run each day on the master node sometime during the two hours after midnight.We have seen a hot threads dump where the
findUnusedStateDocs
part of the daily maintenance is blocking a Netty thread:MlDailyMaintenanceService
is supposed to run in theml_utility
threadpool. We need to audit which thread each part of its work currently runs in, then ensure every stage actually does run in theml_utility
threadpool.Additionally, there must be a flaw in the way
MlDailyMaintenanceService
is tested that means the assertions that actions don't run in network threads are not triggering.The text was updated successfully, but these errors were encountered: