Details
-
Bug
-
Resolution: Fixed
-
Critical
-
6.0.0
-
Untriaged
-
No
Description
Build 6.0.0-1432
Observed high KV ops(gets) on metadata bucket when timers present in cluster to be fired in future.
e.g. Attached is snapshot of kv ops(more than 50K/sec) on metadata bucket where 50M timers present in cluster to be fired after few mins. In this case cluster has 4KV nodes and 1 eventing node, we have 24 workers configured for a function,
Attachments
For Gerrit Dashboard: MB-30814 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
98051,7 | MB-30814 Avoid bucket lookups when span_ceiling > current time | unstable | eventing | Status: MERGED | +2 | +1 |
98106,2 | MB-30814 Update span floor when first timer is created | unstable | eventing | Status: ABANDONED | 0 | 0 |
98118,3 | MB-30814 Pause scan routines for duration aligned with timer resolution | unstable | eventing | Status: MERGED | +2 | +1 |
98124,4 | MB-30814 Expose metastore stats over rest endpoints | unstable | eventing | Status: MERGED | +2 | +1 |
98169,5 | MB-30814 Shrink span if there are no rows left for scan | unstable | eventing | Status: MERGED | +2 | +1 |
98205,3 | MB-30814 Mitigate potential panics during undeploy | unstable | eventing | Status: MERGED | +2 | +1 |