You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/10/04 17:03:20 UTC
[jira] [Commented] (GEODE-1801) nonSingleHopsCount cache-perf
statistic is inaccurate
[ https://issues.apache.org/jira/browse/GEODE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15545974#comment-15545974 ]
ASF subversion and git services commented on GEODE-1801:
--------------------------------------------------------
Commit f686e9e1e5c9c6c543ec70aba94d387e02820643 in incubator-geode's branch refs/heads/feature/e2e-testing from [~ukohlmeyer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=f686e9e ]
Merge branch 'develop' into feature/GEODE-1801
> nonSingleHopsCount cache-perf statistic is inaccurate
> -----------------------------------------------------
>
> Key: GEODE-1801
> URL: https://issues.apache.org/jira/browse/GEODE-1801
> Project: Geode
> Issue Type: Bug
> Components: client/server
> Reporter: Bruce Schuchardt
> Assignee: Udo Kohlmeyer
>
> While working on GEODE-1761 I noticed that this statistic is only updated if the metadata for server partitioned-region bucket location is going to be refreshed. The statistic should actually be incremented any time the servers send a metadata refresh hint in their response. PutOp, DestroyOp, GetOp, etc need to do this in their processResponse() methods and the current increments of the stat in ClientMetadataService should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)