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
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.E-starterMight be suitable for a starter project for new employees or team members.T-kvKV Team
(from an internal conversation)
There are 2 reasons for these log statements:
to know if this switching is happening and how often, in case we need to improve the heuristic in runnable.go.
if we see some weird admission control behavior, we want to be able to tell whether there was any use of the 250ms sampling during that time interval.
Both use cases can be addressed using two cumulative metrics (or preferably one metric with a label) that count the number of 250ms samples and the number of 1ms samples.
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.E-starterMight be suitable for a starter project for new employees or team members.T-kvKV Team
I've seen this in many different experiments:
We should remove/downgrade this log message and add a metric instead.
Jira issue: CRDB-15222
The text was updated successfully, but these errors were encountered: