geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Udo Kohlmeyer (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (GEODE-1801) nonSingleHopsCount cache-perf statistic is inaccurate
Date Wed, 28 Sep 2016 21:38:20 GMT

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

Udo Kohlmeyer reassigned GEODE-1801:
------------------------------------

    Assignee: 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
>            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