Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
Something I observed is that while a subscription queue was "full" the default throttling caused geode to only add 10 events/sec to the queue. This makes sense. But what didn't make sense was that the messageQueueSize did not change by 10 events/sec even though, during this time, nothing was draining from the queue. Then when the draining finally started (because the CacheClientUpdater started running after a long register interest that had been blocking it) we saw a huge spike in messageQueueSize when we should have seen gradual growth.
In addition to improving messageQueueSize it would also be nice to have a gauge stat that shows how many threads are currently trying to add to the queue. The throttle logic can cause a large number of thread to be blocked.
Attachments
Issue Links
- links to