Re: Need Help on understanding vsd files

> > Hi All, > > I am looking at getTime-PartitionedRegionStats using vsd tools. I need > some help on how to interpret following graph. > If there is a document which helps to explain please let me know. > > > [image: Inline image 1] > > > Thanks > Avinash > >

Re: Need Help on understanding vsd files

Attaching the graph. On Thu, Sep 21, 2017 at 2:45 PM, Avinash Dongre wrote: > Hi All, >> >> I am looking at getTime-PartitionedRegionStats using vsd tools. I need >> some help on how to interpret following graph. >> If there is a document which helps to explain please let me know. >> >> >> [ima

Build failed in Jenkins: Geode-nightly #961

See Changes: [abaker] Update version on release branch [abaker] GEODE-2947: Error message is now specific to lucene indexes [jiliao] GEODE-3006: reduce the frequency of ping request and reduce the loglevel [jilia

Build failed in Jenkins: Geode-nightly-flaky #128

See Changes: [abaker] Update version on release branch [abaker] GEODE-2947: Error message is now specific to lucene indexes [jiliao] GEODE-3006: reduce the frequency of ping request and reduce the loglevel

[Vote] Better type checking by moving PdxWrapper from a standard class to a template class.

Hi All, In reviewing the PdxWrapper class it, it seemed like it would be a good move to make this a template class. This will allow better type checking anytime we use it. An example of what is being planned is to change from MyClass object; PdxWrapper((void *) object,...) to PdxWrapper(object,

Re: [Vote] Better type checking by moving PdxWrapper from a standard class to a template class.

Here is a link to my branch in my fork that has the changes on it. https://github.com/mhansonp/geode-native/tree/wip/templatePdxWrapper Thanks, Mark On Thu, Sep 21, 2017 at 10:19 AM, Mark Hanson wrote: > Hi All, > > In reviewing the PdxWrapper class it, it seemed like it would be a good > move

Re: [Vote] Better type checking by moving PdxWrapper from a standard class to a template class.

+1 for type safety Sarge > On 21 Sep, 2017, at 10:21, Mark Hanson wrote: > > Here is a link to my branch in my fork that has the changes on it. > > https://github.com/mhansonp/geode-native/tree/wip/templatePdxWrapper > > Thanks, > Mark > > On Thu, Sep 21, 2017 at 10:19 AM, Mark Hanson wrote

Re: [DISCUSS] Addition of isValid API to Index interface

Scheduling an asynchronous task to drop the index everywhere seems like it's adding a lot of complexity and potential for race conditions. Is it really worth optimizing memory usage in this edge case where we hit an exception updating an index? The objective of these changes is to fix a window wher

Re: Need Help on understanding vsd files

At a high level, you can find stat descriptions by "selecting a stat" and then clicking (in vsd) main->"Show Statistic Info". -Anil. On Thu, Sep 21, 2017 at 2:24 AM, Avinash Dongre wrote: > Attaching the graph. > > On Thu, Sep 21, 2017 at 2:45 PM, Avinash Dongre > wrote: > >> Hi All, >>> >>>

Re: [DISCUSS] Addition of isValid API to Index interface

I agree with Dan and Naba. The possible race conditions seem very risky to me. Memory optimization isn't really needed here because the user has already budgeted memory for the index. They probably weren't trying to create an index that would be corrupted and when it does get corrupted, it won't

Re: New client/server protocol - seeking feedback

I'm curious about few things I see in the .proto files. 1) I see there is a correlationId in the MessageHeader definition. What is that used for? I remember we had a discussion a while back where I thought we had decided that might not be not necessary? 2) I also see a CreateRegionRequest and Des

Re: [DISCUSS] Addition of isValid API to Index interface

Can anyone help me understand the race condition? My understanding was that in addition to setting the isInvalid flag, we fire off a background task to drop the index. This task can use the plumbing that gfsh uses to drop the index. Even if we schedule more than one of these tasks, the later tasks

Re: [Vote] Better type checking by moving PdxWrapper from a standard class to a template class.

Is using PdxWrapper any different than if user added their type into the serialization registry? If not, then do we really want to provide 2 ways to do the same thing? Thanks, David On Thu, Sep 21, 2017 at 10:24 AM, Michael William Dodge wrote: > +1 for type safety > > Sarge > > > On 21 Sep, 2

Re: [Vote] Better type checking by moving PdxWrapper from a standard class to a template class.

It may be work looking into the documentation a little to understand the purpose of the PdxWrapper. On Thu, Sep 21, 2017 at 11:37 AM David Kimura wrote: > Is using PdxWrapper any different than if user added their type into the > serialization registry? If not, then do we really want to provide

Re: [Vote] Better type checking by moving PdxWrapper from a standard class to a template class.

I briefly scanned some docs, but I'm still not sure I follow why this needs to be in our domain. It says PdxWrapper is "for domain objects that you cannot or do not want to modify". Why can't the application create an opaque wrapper around the object that cannot be modified and register that wrap

[ANNOUNCE] Apache Geode 1.2.1

The Apache Geode community is pleased to announce the availability of Apache Geode 1.2.1. Apache Geode is a data management platform that provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high

Re: Need Help on understanding vsd files

You probably need more than just the getTime stat to see whats going on there. That stat is basically telling you how much time per second get operations are occurring. You probably need to also know how many gets are occurring. What I generally do is: - plot time stat (getTime in this case) - di

Re: [Vote] Better type checking by moving PdxWrapper from a standard class to a template class.

As it stands right now this object has some funkiness that makes there tricky I think. It might be worth leaving it alone actually and deprecating it for something different. class MyUnmodifiedClass; class MyUnmodifiedClassPdxSerializer : PdxSerializer { using PdxSerializer::PdxSerializer; My

CacheConnectionTimeoutJUnitTest and ClientHealthMonitorJUnitTest

These two tests seem to be passing/failing about 50/50% of the time. I recommend marking these as FlakyTest while the authors work on making them pass 100% :geode-protobuf:integrationTest org.apache.geode.protocol.acceptance.CacheConnectionTimeoutJUnitTest > testUnresponsiveClientsGetDisconnected

DiskSpaceLimitIntegrationTest moved to FlakyTest

I just moved DiskSpaceLimitIntegrationTest because GEODE-3205 continues to intermittently fail. I've already done a lot work to try and make the test pass consistently but it's going to require a lot more tuning to make sure the files are just the right size so that the StatSampler deletes them at

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #685 has FAILED (2 tests failed). Change made by Mark Paluch.

--- Spring Data GemFire > Nightly-ApacheGeode > #685 failed. --- Scheduled with changes by Mark Paluch. 2/2037 tests failed. https://build.spring.io/browse/SGF-N

Re: Need Help on understanding vsd files

Thanks Barry for your help and explanation. Could you please re-attach the charts for the steps. I do not see them in the email. Thanks Avinash On Fri, Sep 22, 2017 at 2:30 AM, Barry Oglesby wrote: > You probably need more than just the getTime stat to see whats going on > there. That stat is