[
https://issues.apache.org/jira/browse/CASSANDRA-16511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300333#comment-17300333
]
Michael Semb Wever edited comment on CASSANDRA-16511 at 3/12/21, 2:10 PM:
--------------------------------------------------------------------------
CI
- patch as-is ::
https://ci-cassandra.apache.org/job/Cassandra-devbranch-test/303/
- patch w/ runners enabled ::
https://ci-cassandra.apache.org/job/Cassandra-devbranch-test/304/
With runners, ci-cassandra went with two runners:
{code}
…
13:52:30 get-cores:
13:52:30 [echo] Number of cores: 8
13:52:30
13:52:30 get-mem:
13:52:30 [echo] Mem size : 33675816960
13:52:30
13:52:30 testclasslist:
13:52:30 [echo] Number of test runners: 2
…
{code}
And to [expectation|https://issues.apache.org/jira/browse/CASSANDRA-13078],
this halved the build time, from ~2 hours to ~1 hour.
And no failures.
was (Author: michaelsembwever):
CI
- patch as-is ::
https://ci-cassandra.apache.org/job/Cassandra-devbranch-test/303/
- patch w/ runners enabled ::
https://ci-cassandra.apache.org/job/Cassandra-devbranch-test/304/
With runners, ci-cassandra went with two runners:
{code}
…
13:52:30 get-cores:
13:52:30 [echo] Number of cores: 8
13:52:30
13:52:30 get-mem:
13:52:30 [echo] Mem size : 33675816960
13:52:30
13:52:30 testclasslist:
13:52:30 [echo] Number of test runners: 2
…
{code}
And to expectation, this halved the build time, from ~2 hours to ~1 hour.
And no failures.
> Running tests in parallel can sometimes result in port collision
> ----------------------------------------------------------------
>
> Key: CASSANDRA-16511
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16511
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
> Fix For: 4.0.x
>
> Attachments: screenshot-1.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When running unit tests with parallel execution we may sometimes notice the
> port collision. In this mode, test classes from the list get consecutive
> offsets which are added to native transport port, storage port and ssl
> storage port ( {{OffsetAwareConfigurationLoader}} ). However we add to the
> ports configured in {{test/conf/cassandra.yaml}} we as we can see we have the
> following default config:
> {code:java}
> storage_port: 7012
> ssl_storage_port: 7011 {code}
> This results in the situation that thread n has the same storage port as
> thread n+1 has ssl storage port. There are not much such tests, but we can
> see {{ConnectionTests}} failing frequently because of that.
> The other problem is that {{OffsetAwareConfigurationLoader}} does not adjust
> native transport ssl port.
> !screenshot-1.png!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
