[GEODE-2017] Removal of nonSingleHopsCount stat in client

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Component/s: client/server, docs
• Assignee: Udo Kohlmeyer
• Reporter: Udo Kohlmeyer
• Created: 19/Oct/16 19:51
• Updated: 20/Apr/18 19:53
• Resolved: 07/Nov/16 20:23

Description

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.

Issue Links

• relates to: GEODE-1801 nonSingleHopsCount cache-perf statistic is inaccurate
• relates to: GEODE-2763 Remove of nonSingleHopsCount stat in client