[
https://issues.apache.org/jira/browse/GEODE-9074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400595#comment-17400595
]
ASF subversion and git services commented on GEODE-9074:
--------------------------------------------------------
Commit a10a56f573e9a4aabf3c5b6e3862539d6dd93b92 in geode's branch
refs/heads/develop from Mario Ivanac
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a10a56f ]
GEODE-9074: Added update of messageQueueSize at putting message to qu… (#6445)
* GEODE-9074: Added update of messageQueueSize at putting message to queue.
Also added new statistics messagesBeingQueuedInProgress and
messagesBeingQueuedTime.
> CacheClientProxyStatistics messageQueueSize does not increase as events are
> added
> ---------------------------------------------------------------------------------
>
> Key: GEODE-9074
> URL: https://issues.apache.org/jira/browse/GEODE-9074
> Project: Geode
> Issue Type: Bug
> Components: client queues
> Reporter: Darrel Schneider
> Assignee: Mario Ivanac
> Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
