Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
isaac.lambatisaac.lambatReporter
isaac.lambatisaac.lambatStory Points
1Components
Sprint
NoneFix versions
Priority
MajorInstabug
Open Instabug
Details
Details
Assignee
isaac.lambat
isaac.lambatReporter
isaac.lambat
isaac.lambatStory Points
1
Components
Sprint
None
Fix versions
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created March 21, 2022 at 5:54 PM
Updated October 15, 2024 at 3:07 PM
Resolved May 10, 2022 at 5:37 PM
The
NumPullReplActiveOneShot
stat is not decremented when a one shot sub changes request has finished pulling and sending the sub changes. It will decrement when closing the Blip client provided it has NOT been reused.Reusing the Blip client causes the decrement code not to run as it is only ran when closing the client. This code is in function
(bsc *BlipSyncContext) Close()
.Running a one-shot before reusing the blip client for a continuous changes feed will cause the
continuous
to be replaced meaning that even when the Blip client is closed, the one shot active stats don't get decremented accordingly.A potential solution to this is to decrement the one shot stat for Blip
SubChangesOneShotActive
(which is used for the db statNumPullReplActiveOneShot
) when the one shot has sent the results instead of doing it when the Blip client is closed.