Resource Intensive and Upgrade tests (Dtest Cassandra)

[Rajiv Dimri <ra...@oracle.com>]

Hi All,

 

We have setup a dtest environment to run against Cassandra db version 3.11.1 and 3.0.5

During the test run we see that tests under the category of 

Resource intensive and Upgrade tests

Are skipped by default during the collection phase.

 

And this is a huge number (1100+ out of the 1900+ tests written) more than 50%

 

If we have to enable these tests then we have to use '--force-resource-intensive-tests' and '--execute-upgrade-tests' option.

 

My questions are as below:

Do you recommend, turning on these tests using the options above?

Are there any special case/scenarios when these tests need to be run?

What should be the minimum system configuration for the resource intensive tests to run without any issues?

 

Regards,

Rajiv 

 

Re: Resource Intensive and Upgrade tests (Dtest Cassandra)

[kurt greaves <ku...@instaclustr.com>]

Moving thread to dev.

We have setup a dtest environment to run against Cassandra db version
> 3.11.1 and 3.0.5
> During the test run we see that tests under the category of
> Resource intensive and Upgrade tests
> Are skipped by default during the collection phase.

FWIW you can see these results for the tests (excluding upgrade tests) on
the ASF jenkins here: https://builds.apache.org/view/A-D/view/Cassandra/
(dtest-large jobs are resource-intensive)

Do you recommend, turning on these tests using the options above?

IMO those options suck. I've got a patch which provides some options that
will *only* run the resource-intensive and/or upgrade tests. The current
ones will run all non-resource-intensive plus resource-intensive (and same
for upgrade tests). Having said that this is probably fine if you don't
care how long the tests take and you have a big enough machine, but you're
looking at well over 20 hours of running tests and praying nothing goes
wrong in that time.
Patch is on CASSANDRA-14443
<https://issues.apache.org/jira/browse/CASSANDRA-14443> if you're
interested.

> Are there any special case/scenarios when these tests need to be run?

We should be running them all the time/before any commit, but the testing
environment isn't really in a good position for that at the moment. We'll
be working on this for 4.0.

What should be the minimum system configuration for the resource intensive
> tests to run without any issues?

For resource-intensive you'll need at least 32gb of RAM and at least a 4
core machine to run them reliably. Upgrade tests are currently not
completely working and you're probably best avoiding them for now.


On 21 May 2018 at 05:11, Rajiv Dimri <ra...@oracle.com> wrote:

> Hi All,
>
>
>
> We have setup a dtest environment to run against Cassandra db version
> 3.11.1 and 3.0.5
>
> During the test run we see that tests under the category of
>
> Resource intensive and Upgrade tests
>
> Are skipped by default during the collection phase.
>
>
>
> And this is a huge number (1100+ out of the 1900+ tests written) more than
> 50%
>
>
>
> If we have to enable these tests then we have to use
> ‘--force-resource-intensive-tests’ and ‘--execute-upgrade-tests’ option.
>
>
>
> My questions are as below:
>
> Do you recommend, turning on these tests using the options above?
>
> Are there any special case/scenarios when these tests need to be run?
>
> What should be the minimum system configuration for the resource intensive
> tests to run without any issues?
>
>
>
> Regards,
>
> Rajiv
>
>
>