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
Please note that there are many players who can pause op processing:
DeltaScheduler
ScheduleManager
Summarizer
Container (code proposal)
Given that API is generic and is available to all layers, more users may show up later.
From @vladsud
Add a system to track who's pausing ops, and a way to expose first/last/maybe all actors who caused ops to sit paused
I'd suggest for pause() to take some token (string, better - assert tag, clearly representing call site) and return another token (coutner). And for resume() to require token returned from pause() to match them and keep tracking who keeps queue paused. That would give us full picture and enforcement that pause() & resume are properly paired (and if not - we always know the offender)
A simpler system might be for resume() to accept token (like assert tag) to clearly articulate who was the last one to resume op processing, and thus we can log it with duration. This is less powerful system, but much simpler to implement for this task.
Please note that there are many players who can pause op processing:
Given that API is generic and is available to all layers, more users may show up later.
From @vladsud
Add a system to track who's pausing ops, and a way to expose first/last/maybe all actors who caused ops to sit paused
Originally posted by @vladsud in #8912 (comment)
The text was updated successfully, but these errors were encountered: