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
MinPinnedVersionId not increase when there's no batch queries running #16644
Comments
@zwang28 @Little-Wallace randomly assigned to you. Feel free to find someone else to check this issue |
unpin every 3 hours is force by |
Note down some observations of today's case: Name: MinPinnedVersionIdNotIncrease Sev: [warning] Cluster: [prod-aws-euno1-eks-a] at 10:04 AM. Min-pinned version ID was stuck: Meanwhile, pinned epoch IDs were normal: Barrier was abnormal, but it's after the 1st min-epoch stuck. Thus, it's likely to be a result instead of the cause. There was no heavy batch queries.
The stuck at 7:58 AM, which I consider as the root cause, was caused by a sink error:
|
The hummock version is pinned by log store. It's consistently held due to the large volume of historical logs to consume, until forcefully unpinned by The log input rate of sink exceeds the consumption rate, so the situation will deteriorate. |
background:
https://risingwave-labs.slack.com/archives/C034TRN6A49/p1714528348327289
During oncall, we found MinPinnedVersionIdNotIncrease alert keeps firing for a cluster. The version id increase only every 3 hours.
Grafana indicates that there were no batch queries running.
So it's weird that the version id has been pinned for such an extended period.
Not sure if this is a bug. If it's not, maybe we should remove this alert.
The text was updated successfully, but these errors were encountered: