geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-1801) nonSingleHopsCount cache-perf statistic is inaccurate
Date Tue, 11 Oct 2016 20:36:20 GMT

    [ https://issues.apache.org/jira/browse/GEODE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15566518#comment-15566518
] 

ASF subversion and git services commented on GEODE-1801:
--------------------------------------------------------

Commit 75d8c3f5d2c0ca6f1aa399b4d9493d0c4b1e2fb3 in incubator-geode's branch refs/heads/feature/GEODE-1801
from [~ukohlmeyer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=75d8c3f ]

GEODE-1801: Amended some changes


> 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)

Mime
View raw message