geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Udo Kohlmeyer (JIRA)" <>
Subject [jira] [Created] (GEODE-2017) Removal of nonSingleHopsCount stat in client
Date Wed, 19 Oct 2016 19:51:59 GMT
Udo Kohlmeyer created GEODE-2017:

             Summary: Removal of nonSingleHopsCount stat in client
                 Key: GEODE-2017
             Project: Geode
          Issue Type: Bug
          Components: client/server, native client
            Reporter: 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

This message was sent by Atlassian JIRA

View raw message