-
Notifications
You must be signed in to change notification settings - Fork 882
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
Multi-cursor: pending task count monitoring & mitigation #3275
Conversation
} else { | ||
nextReader = readerGroup.NewReader(readerID+1, splitSlices...) | ||
} | ||
nextReader.Pause(clearSliceThrottleDuration) |
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.
why pause here? (for 10s?)
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.
Because we just did an unloading, without pause those tasks may be loaded back immediately.
Although nextReader
will use a lower max task count so it won't trigger another unloading, but I think it will still increase the chance of another unloading. So pausing for a while and let some in memory tasks get processed first before attempting another load.
AlertType AlertType | ||
AlertAttributesReaderStuck *AlertAttributesReaderStuck | ||
AlertType AlertType | ||
AlertAttributesQueuePendingTaskCount *AlertAttributesQueuePendingTaskCount |
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.
nit: remove Queue from the type name and variable name?
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.
Added Queue
in the names since we may/will monitor # of pending tasks on a host level in the future, so want to avoid naming confusion when we do that.
What changed?
Why?
How did you test it?
Potential risks
Is hotfix candidate?