+1 for removing it
It's redundant, we've rarely used client statistics and I hear that
people generally have stats turned off in clients anyway.
Le 10/19/2016 à 12:55 PM, Udo Kohlmeyer a écrit :
Hi there Guys,
I've created https://issues.apache.org/jira/browse/GEODE-2017 to track
the removal of the nonSingleHopCount stat from the client, as it is
potentially a redundant stat.
From the implementation it only increments on "singleHop" enabled
pools when an operation requires more than one hop to complete. This
exact same metric is tracked in "metaDataRefreshCount", which tracks
the amount of meta data refreshes on the client. Which is
automatically refreshed when an operation requires more than one hop.
Does anyone have any objection in the removal of this stat?
--Udo
