[
https://issues.apache.org/jira/browse/GEODE-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16842520#comment-16842520
]
ASF subversion and git services commented on GEODE-6776:
--------------------------------------------------------
Commit 7d13f37e4c662e96086ebfd3b47195bcad36e439 in geode's branch
refs/heads/develop from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7d13f37 ]
GEODE-6776: fix ClientStats and ClientSendStats (#3594)
"sendStats" is now used instead of "stats" which is what caused the bug.
A unit test now exists that checks that the correct send stats are incremented.
> ClientSendsStats and ClientStats are broken
> -------------------------------------------
>
> Key: GEODE-6776
> URL: https://issues.apache.org/jira/browse/GEODE-6776
> Project: Geode
> Issue Type: Bug
> Components: statistics
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A bunch of ClientSendStats are always zero. All of the stats whose name ends
> with "SendTime" will always be zero. The stats named
> "getPDXIdForTypeSendFailures" and "getPDXIdForTypeSendsSuccessful" will also
> always be zero.
> The values for these stats may get recorded, but in the wrong spot. So this
> can mess up ClientStats. For example getsSendTime is recorded in
> ClientStats.gets. So instead of "gets" showing you the number of get calls,
> it has the number of nanos it took to send the get to the server. Which stats
> may have wrong values in ClientStats are too many to itemize. Just be aware
> that ClientStats in general may be wrong due to this bug.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
