You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Udo Kohlmeyer (JIRA)" <ji...@apache.org> on 2016/09/19 21:57:21 UTC

[jira] [Updated] (GEODE-1801) nonSingleHopsCount cache-perf statistic is inaccurate

     [ https://issues.apache.org/jira/browse/GEODE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Udo Kohlmeyer updated GEODE-1801:
---------------------------------
    Assignee:     (was: Udo Kohlmeyer)

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