[
https://issues.apache.org/jira/browse/GEODE-8876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433581#comment-17433581
]
ASF subversion and git services commented on GEODE-8876:
--------------------------------------------------------
Commit 17a67bc6397890f10696410fcb6a1798031fcf6c in geode's branch
refs/heads/develop from Jakov Varenina
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=17a67bc ]
Revert "GEODE-8876: Statistics not collecting correct value for gets when tra…
(#6199)" (#7027)
This reverts commit 5dde7d765c252ef20cfb16981b18e68903e32165 that caused
GEODE-9760
> Statistics not collecting correct value for gets when transaction is used
> -------------------------------------------------------------------------
>
> Key: GEODE-8876
> URL: https://issues.apache.org/jira/browse/GEODE-8876
> Project: Geode
> Issue Type: Bug
> Components: statistics, transactions
> Reporter: Mario Kevo
> Assignee: Jakov Varenina
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {color:#172b4d}We were running traffic with reads and updates using
> transactions. After traffic finished we collected statistic file from the
> server pods.{color}
> {color:#172b4d}After opening stats file we got the following:{color}
> * {color:#172b4d}In the CacheSeverStats statistics, counters for getRequest
> and putRequest are showing correct number of get and put operations requested
> by client.{color}
> * {color:#172b4d}In the *CachePerfStats*, graph for puts during traffic time
> is showing expected number of put operation, but the graph for *gets* was
> *empty* in that period!{color}
> {color:#172b4d}We tried to check the same statistics for traffic generated
> without using transactions and statistic for gets was showing correct number
> of operations.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
