Hi, I do not yet have an automatic test but this is the client code I am using:
package org.apache.geode_examples.overload; import org.apache.geode.cache.Region; import org.apache.geode.cache.client.ClientCache; import org.apache.geode.cache.client.ClientCacheFactory; import org.apache.geode.cache.client.ClientRegionShortcut; import org.apache.geode.pdx.ReflectionBasedAutoSerializer; public class SimpleClient { public static void main(String[] args) { ClientCache cache = new ClientCacheFactory().addPoolLocator("127.0.0.1", 10334) .setPoolReadTimeout(10).setPoolRetryAttempts(1) .setPdxSerializer(new ReflectionBasedAutoSerializer("org.apache.geode_examples.overload.*")) .set("log-level", "WARN").create(); Region region = cache.createClientRegionFactory(ClientRegionShortcut.PROXY).create("overload"); region.get(args[0]); cache.close(); } } Thanks, /Alberto On 17/5/19 17:59, pulkit chandra wrote: Best to share the test case code with the community. Pulkit Chandra 412-641-9176 On Fri, May 17, 2019 at 11:37 AM Anthony Baker <aba...@pivotal.io<mailto:aba...@pivotal.io>> wrote: What’s the redundancy and how many members are in the cluster? Are you using single-hop? Thanks, Anthony On May 17, 2019, at 12:15 AM, Alberto Gomez <alberto.go...@est.tech<mailto:alberto.go...@est.tech>> wrote: Hi Geode community, Running some queries on a partitioned region I have noticed some behavior for the hitCount and missCount counters that does not look right to me: If I retrieve an entry present in the region from gfsh using get, the hitCounter is incremented once and the missCounter is not incremented. But, if I run the same get from a java client (using ClientRegionShortcut.PROXY), what I see is that the hitCount is incremented once but also the missCount is incremented once. The hitCount is always incremented on the server hosting the bucket where the entry is stored while the missCount, sometimes is incremented on that same server while others it is incremented on the server not hosting the bucket. Is this a bug in Geode or could there an explanation for the different behavior depending on the client? Thanks in advance, /Alberto