Re: Concurrent tests hitting OOME, hangs, etc

I like the idea of a separate concurrency test suite. We have other tests of concurrency that aren't using this runner that could also go there - maybe we could establish some good conventions and figure out how to give more CPU time to these tests. I'd actually like to see *more* tests of concurre

Re: Concurrent tests hitting OOME, hangs, etc

> On Apr 16, 2020, at 2:16 PM, Kirk Lund wrote: > Anyone else up for moving them to new src sets? Unfortunately, this alone > won't make the tests work with the newer versions of Mockito -- and guess > what, they only OOME in the cloud (not locally). I could take a stab at it since I split up

Concurrent tests hitting OOME, hangs, etc

The concurrent tests (tests using the ConcurrentTestRunner from geode-concurrency-test) are currently blocking both of my PRs. 1st PR is upgrading Mockito -- several Concurrent Tests use Mockito but the runner executes too many tests in parallel and Mockito can't keep up with it -- they hit OOME a

Re: [Discuss] Cache.close synchronous is not synchronous, but code still expects it to be....

It timed out while running OldFreeListOffHeapRegionJUnitTest but I think the tests before it were responsible for the timeout being exceeded. I looked through all of the previously run tests and how long each but without having some sort of database with how long each test takes, it's impossible to

Re: [Discuss] Cache.close synchronous is not synchronous, but code still expects it to be....

Kirk, most IntegrationTest jobs run in 25-30 minutes, but I did see one that came in just under 45 minutes but did succeed. It would be nice to know what test is occasionally

Re: Data ingestion with predefined buckets

>> PutAllPRMessage.* These are internal APIs/message protocols used to handle PartitionedRegin messages. The messages are sent from originator node to peer nodes to operate on a given partitioned region; not intended as application APIs. We could consider, looking at the code, which determines bu

Re: [Discuss] Cache.close synchronous is not synchronous, but code still expects it to be....

The time out is increased in the shared Jinja variables file On Thu, Apr 16, 2020, 10:48 Kirk Lund wrote: > I revived my branch by rebasing it on develop and filed a new draft PR: > > https://github.com/apache/geode/pull/4963 > > Unfortunately, IntegrationTest exceeds timeout every time I trigge

Re: [Discuss] Cache.close synchronous is not synchronous, but code still expects it to be....

I revived my branch by rebasing it on develop and filed a new draft PR: https://github.com/apache/geode/pull/4963 Unfortunately, IntegrationTest exceeds timeout every time I trigger it. The cause does not appear to be a specific test or hang. I think IntegrationTest has already been running very

Re: About Geode rolling downgrade

-1 Another reason that we should not support rolling downgrade is that it makes it impossible to upgrade distributed algorithms. When we added rolling upgrade support we pretty much immediately ran into a distributed hang when a test started a Locator using an older version. In that release w

Re: [Discuss] Cache.close synchronous is not synchronous, but code still expects it to be....

I've run into the CacheExistsException problem that John mentioned many times, or the associated "A connection to a distributed system already exists in this VM" exception thrown by InternalDistributedSystem. On 4/14/20, 4:02 PM, "John Blum" wrote: Among other problems I encountered, 1

About Geode rolling downgrade

Hi, Some months ago I posted a question on this list (see [1]) about the possibility of supporting "rolling downgrade" in Geode in order to downgrade a Geode system to an older version, similar to the "rolling upgrade" currently supported. With your answers and my investigations my conclusion w

Re: Reviewers for GEODE-7971 Gateway sender to deliver transaction events atomically to gateway receivers

Hi, Friendly reminder - No reviewers yet for this PR. -Alberto G. From: Alberto Gomez Sent: Tuesday, April 14, 2020 3:34 PM To: dev@geode.apache.org Subject: Reviewers for GEODE-7971 Gateway sender to deliver transaction events atomically to gateway receivers