[
https://issues.apache.org/jira/browse/KUDU-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135870#comment-16135870
]
Todd Lipcon commented on KUDU-2105:
-----------------------------------
I think a nice improvement would be to add an 'extra-long' test mode. Currently
we either run our tests with ALLOW_SLOW_TESTS=1 or 0. The "slow tests" are used
for precommit, so we still don't allow them to be more than a couple minutes.
We could change the env var to have more available lengths, eg with a
KUDU_TEST_LENGTH variable or somesuch. I like the classification that Bazel
uses (see https://docs.bazel.build/versions/master/test-encyclopedia.html ) for
example.
Then we could take some of our existing tests mentioned above and give them a
different set of parameters when run in long/eternal modes, and set up some job
which runs them once a day or somesuch.
> Create single node stress test framework
> ----------------------------------------
>
> Key: KUDU-2105
> URL: https://issues.apache.org/jira/browse/KUDU-2105
> Project: Kudu
> Issue Type: Test
> Components: perf
> Reporter: Edward Fancher
> Assignee: Edward Fancher
>
> It would be useful to have single node stress test support.
> 1. To allow node density testing without multi node cluster support.
> 2. To allow general perf testing without multi node cluster support.
> 3. To be able to run performance tests which have less variance (due to
> network noise).
> 4. (nice, but not needed) be able to simulate various characteristics such as
> network reliability, rpc call failures, under stress without needing to
> modify processes on other nodes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
