[
https://issues.apache.org/jira/browse/GEODE-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630775#comment-15630775
]
ASF subversion and git services commented on GEODE-2017:
--------------------------------------------------------
Commit 47d295cb2aa7931007188b2c31ee443b46c4c357 in incubator-geode's branch
refs/heads/feature/GEODE-2017 from [~ukohlmeyer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=47d295c ]
GEODE-2017: Remove nonPRSingleHop stat from client
> Removal of nonSingleHopsCount stat in client
> --------------------------------------------
>
> Key: GEODE-2017
> URL: https://issues.apache.org/jira/browse/GEODE-2017
> Project: Geode
> Issue Type: Bug
> Components: client/server, native client
> Reporter: Udo Kohlmeyer
> Assignee: Udo Kohlmeyer
>
> Currently, the nonSingleHopsCount stat in the client is defined as "Total
> number of times client request observed more than one hop during operation."
> From this definition, this stat should track every time a client operation
> requires more than one hop. Currently, this stat is only incremented when
> "singleHop" is enabled on the pool. If this is correct then
> metaDataRefreshCount will track the same metric, as the client will
> automatically refresh when more than one hop is required for a prSingleHop
> enabled pool.
> If the nonSingleHopsCount metric where to track every non-one hop operation,
> regardless of the "singleHop" flag on the pool, then the implementation of
> this stat would need to change.
> Otherwise we remove this stat and only track all nonSingleHop operation with
> the metaDataRefresh count.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
