We are using geode 1.8.0. With best regards, Ashish
On Thu, Jul 9, 2020, 10:18 PM aashish choudhary < aashish.choudha...@gmail.com> wrote: > Hi, > > We are seeing lot of Thread Contention issue via invoking geode > functions. We have enabled Appdynamics transaction monitoring which points > to below geode internal classes with method which are taking too long. > > > > Thread Contention on this call > > > org.apache.geode.internal.cache.execute.PartitionedRegionFunctionResultSender:lastResult > Blocked on > org.apache.geode.internal.cache.execute.PartitionedRegionFunctionResultSender@3501a829 > > Class org.apache.geode.internal.cache.execute. > PartitionedRegionFunctionResultSender > > Method > > lastResult > > Time taken:- 1,664ms > > > Class org.apache.geode.internal.HeapDataOutputStream > > Method sendTo > > Time taken:- 27,525ms > > > Then in this case there are repeated calls like this while put operation > > Class org.apache.geode.internal.cache.PartitionedRegion > > Method putInBucket > > Class > > java.lang.Thread > > sleep > > java.lang.Thread > > sleep > > java.lang.Thread > > sleep > > Is this an environmental issue or some configuration tuning is required > over here. Why would geode internal method calls take so much time? > > Thanks, > Ashish >
