Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
2.8.0
-
Security Level: Public
-
None
-
CBG Sprint 74
-
2
Description
SetIfMax logic is incorrect and results in stat values being _much _higher than expected for high_seq_feed and cbl_replication_pull.max_pending
Same thing on SgwFloatStat.SetIfMax - although the method is unused so doesn't impact any stats.
Attachments
Issue Links
- is cloned by
-
CBG-1451 [2.8.3 Backport] SgwIntStat.SetIfMax incorrectly sums old and new values
-
- Closed
-
Build sync_gateway-3.0.0-199 contains sync_gateway commit 0e25fd6 with commit message:
CBG-1438: SetIfMax fix (#5003)