[jira] [Updated] (CASSANDRA-14609) Update circleci builds/env to support java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-14609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-14609: Resolution: Duplicate Status: Resolved (was: Open) This was done as part of CASSANDRA-14806 > Update circleci builds/env to support java 11 > - > > Key: CASSANDRA-14609 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14609 > Project: Cassandra > Issue Type: Task > Components: Legacy/Testing >Reporter: Jason Brown >Assignee: Sumanth Pasupuleti >Priority: Normal > Labels: Java11 > Fix For: 4.0 > > > CASSANDRA-9608 introduced java 11 support, and it needs to be added to the > circleci testing environment. This is a place marker for that work. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15108) Support building Cassandra with JDK 11
[ https://issues.apache.org/jira/browse/CASSANDRA-15108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-15108: Test and Documentation Plan: I've just been testing with circle. Once it's committed, some more detailed performance testing would be useful. Status: Patch Available (was: Open) |[trunk|https://github.com/bdeggleston/cassandra/tree/15108]|[dtests|https://github.com/bdeggleston/cassandra-dtest/tree/jdk11]|[j8 circle|https://circleci.com/workflow-run/4fd48a55-24cc-4920-bdb4-6e8a1c8ff90e]|[j11 circle|https://circleci.com/workflow-run/0655865d-ff5b-4bc8-a1ff-b705c63a40ed]| This changes around how build.xml handles different jdks. The JDK you want to build with is selected with $JAVA_HOME. JDK8 will work as before, but attempting to build with JDK11 will fail unless you signal it’s intentional by either setting the flag -Duse.jdk=11 and/or setting the env var $CASSANDRA_USE_JDK11. Attempting to build with JDK8 will fail with these flags set. The commits are divided into about 3 parts. First is the actual build.xml changes to support jdk11 build (and update intellij files). Second is various adjustments to libraries and command flags to make C* and it’s tests work properly with jdk11. Third is changes to circle ci configs to support building and testing jdk8 and jdk11. This also fixes several dtests that were failing since CASSANDRA-9608 > Support building Cassandra with JDK 11 > -- > > Key: CASSANDRA-15108 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15108 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Blake Eggleston >Assignee: Blake Eggleston >Priority: Normal > > With the changes in java 8 support and licensing, we should be able to build > and run Cassandra with java 11. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15108) Support building Cassandra with JDK 11
[ https://issues.apache.org/jira/browse/CASSANDRA-15108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-15108: Complexity: Normal Change Category: Operability Status: Open (was: Triage Needed) > Support building Cassandra with JDK 11 > -- > > Key: CASSANDRA-15108 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15108 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Blake Eggleston >Assignee: Blake Eggleston >Priority: Normal > > With the changes in java 8 support and licensing, we should be able to build > and run Cassandra with java 11. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15105) Flaky unit test AuditLoggerTest
[ https://issues.apache.org/jira/browse/CASSANDRA-15105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Per Otterström updated CASSANDRA-15105: --- Reviewers: Vinay Chella Status: Review In Progress (was: Patch Available) > Flaky unit test AuditLoggerTest > --- > > Key: CASSANDRA-15105 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15105 > Project: Cassandra > Issue Type: Bug > Components: Legacy/CQL >Reporter: Per Otterström >Assignee: Per Otterström >Priority: Normal > Fix For: 4.0 > > > Depending on execution order some tests will fail in the AuditLoggerTest > class. Any test case that happens to execute after > testExcludeSystemKeyspaces() will typically fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15088) PagingTest failure on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-15088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Per Otterström updated CASSANDRA-15088:
---
Test and Documentation Plan: NA
Status: Patch Available (was: Open)
> PagingTest failure on trunk
> ---
>
> Key: CASSANDRA-15088
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15088
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Marcus Olsson
>Assignee: Marcus Olsson
>Priority: Normal
> Fix For: 4.0
>
> Attachments: 15088-trunk.txt
>
>
> [Example failure|https://circleci.com/gh/emolsson/cassandra/19]
> {noformat}
> java.lang.RuntimeException: Unable to gossip with any peers
> at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1546)
> at
> org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:553)
> at
> org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:841)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:699)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:650)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:379)
> at
> org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:501)
> at
> org.apache.cassandra.service.EmbeddedCassandraService.start(EmbeddedCassandraService.java:50)
> at org.apache.cassandra.cql3.PagingTest.setup(PagingTest.java:63)
> {noformat}
> Running the test case by itself won't reproduce the issue:
> {noformat}
> ant test -Dtest.name=PagingTest
> {noformat}
> But running it in parallel with other tests will:
> {noformat}
> ant test -Dtest.name=cql3/*
> {noformat}
> From the logs the following can be observed:
> {noformat}
> INFO [main] 2019-04-11 15:32:29,916 Node
> configuration:[...seed_provider=org.apache.cassandra.locator.SimpleSeedProvider{seeds=127.0.0.1:7017};
> storage_port=7027]
> ...
> DEBUG [main] 2019-04-17 10:11:55,418 connection attempt 0 to 127.0.0.1:7044
> (GOSSIP)
> DEBUG [main] 2019-04-17 10:11:55,420 creating outbound bootstrap to peer
> 127.0.0.1:7044, compression: false, encryption: disabled, coalesce: DISABLED,
> protocolVersion: 12
> DEBUG [ScheduledFastTasks:1] 2019-04-17 10:11:55,538 connection attempt 1 to
> 127.0.0.1:7044 (GOSSIP)
> DEBUG [ScheduledFastTasks:1] 2019-04-17 10:11:55,538 creating outbound
> bootstrap to peer 127.0.0.1:7044, compression: false, encryption: disabled,
> coalesce: DISABLED, protocolVersion: 12
> {noformat}
> It seems like we have an offset issue of 10 between seed/storage_port.
> The port 7044 does not seem to be defined anywhere though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15088) PagingTest failure on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-15088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Per Otterström updated CASSANDRA-15088:
---
Reviewers: Per Otterström, Vinay Chella (was: Per Otterström)
> PagingTest failure on trunk
> ---
>
> Key: CASSANDRA-15088
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15088
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Marcus Olsson
>Assignee: Marcus Olsson
>Priority: Normal
> Fix For: 4.0
>
> Attachments: 15088-trunk.txt
>
>
> [Example failure|https://circleci.com/gh/emolsson/cassandra/19]
> {noformat}
> java.lang.RuntimeException: Unable to gossip with any peers
> at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1546)
> at
> org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:553)
> at
> org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:841)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:699)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:650)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:379)
> at
> org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:501)
> at
> org.apache.cassandra.service.EmbeddedCassandraService.start(EmbeddedCassandraService.java:50)
> at org.apache.cassandra.cql3.PagingTest.setup(PagingTest.java:63)
> {noformat}
> Running the test case by itself won't reproduce the issue:
> {noformat}
> ant test -Dtest.name=PagingTest
> {noformat}
> But running it in parallel with other tests will:
> {noformat}
> ant test -Dtest.name=cql3/*
> {noformat}
> From the logs the following can be observed:
> {noformat}
> INFO [main] 2019-04-11 15:32:29,916 Node
> configuration:[...seed_provider=org.apache.cassandra.locator.SimpleSeedProvider{seeds=127.0.0.1:7017};
> storage_port=7027]
> ...
> DEBUG [main] 2019-04-17 10:11:55,418 connection attempt 0 to 127.0.0.1:7044
> (GOSSIP)
> DEBUG [main] 2019-04-17 10:11:55,420 creating outbound bootstrap to peer
> 127.0.0.1:7044, compression: false, encryption: disabled, coalesce: DISABLED,
> protocolVersion: 12
> DEBUG [ScheduledFastTasks:1] 2019-04-17 10:11:55,538 connection attempt 1 to
> 127.0.0.1:7044 (GOSSIP)
> DEBUG [ScheduledFastTasks:1] 2019-04-17 10:11:55,538 creating outbound
> bootstrap to peer 127.0.0.1:7044, compression: false, encryption: disabled,
> coalesce: DISABLED, protocolVersion: 12
> {noformat}
> It seems like we have an offset issue of 10 between seed/storage_port.
> The port 7044 does not seem to be defined anywhere though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15108) Support building Cassandra with JDK 11
[ https://issues.apache.org/jira/browse/CASSANDRA-15108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-15108: Reviewers: Dinesh Joshi, Sam Tunnicliffe > Support building Cassandra with JDK 11 > -- > > Key: CASSANDRA-15108 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15108 > Project: Cassandra > Issue Type: Improvement > Components: Build >Reporter: Blake Eggleston >Assignee: Blake Eggleston >Priority: Normal > > With the changes in java 8 support and licensing, we should be able to build > and run Cassandra with java 11. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15108) Support building Cassandra with JDK 11
Blake Eggleston created CASSANDRA-15108: --- Summary: Support building Cassandra with JDK 11 Key: CASSANDRA-15108 URL: https://issues.apache.org/jira/browse/CASSANDRA-15108 Project: Cassandra Issue Type: Improvement Components: Build Reporter: Blake Eggleston Assignee: Blake Eggleston With the changes in java 8 support and licensing, we should be able to build and run Cassandra with java 11. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-15105) Flaky unit test AuditLoggerTest
[
https://issues.apache.org/jira/browse/CASSANDRA-15105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16829623#comment-16829623
]
Per Otterström edited comment on CASSANDRA-15105 at 5/2/19 4:41 PM:
Issue is triggered by audit events collected in {{InMemoryAuditLogger}} which
remain after the execution of {{testExcludeSystemKeyspaces()}}.
[Patch|https://github.com/eperott/cassandra/tree/15105-trunk]
[Unit
Tests|https://circleci.com/gh/eperott/cassandra/53#queue-placeholder/containers/2]
was (Author: eperott):
Issue is triggered by audit events collected in ```InMemoryAuditLogger``` which
remain after the execution of ```testExcludeSystemKeyspaces()```.
[Patch|https://github.com/eperott/cassandra/tree/15105-trunk]
[Unit
Tests|https://circleci.com/gh/eperott/cassandra/53#queue-placeholder/containers/2]
> Flaky unit test AuditLoggerTest
> ---
>
> Key: CASSANDRA-15105
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15105
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/CQL
>Reporter: Per Otterström
>Assignee: Per Otterström
>Priority: Normal
> Fix For: 4.0
>
>
> Depending on execution order some tests will fail in the AuditLoggerTest
> class. Any test case that happens to execute after
> testExcludeSystemKeyspaces() will typically fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15088) PagingTest failure on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-15088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831560#comment-16831560
]
Per Otterström commented on CASSANDRA-15088:
{quote}I can fix a patch that aligns the fields but I'm not sure that it's
worth to do it for all fields (as long as the test cases are working as
intended). Some test cases i.e.
test/unit/org/apache/cassandra/cql3/PstmtPersistenceTest.java uses the
parameter prepared_statements_cache_size_mb: 1 from cassandra.yaml which I
don't believe is necessary for test cases using cassandra-murmur.yaml
(currently at least). To try to keep these two files aligned will probably be
hard to remember as they have already diverged. We could of course add a
comment in the yaml files saying that the fields should be aligned but that can
still be missed.
{quote}
Fair point, over time things will probably diverge any way. Comments will be
overlooked, so don't think that's going to make a loot of difference long term.
Either way, priority at this point should be to get stable tests.
{quote}But instead of keeping the two yaml files aligned perhaps a better
approach would be to have only one yaml file that all test cases depend on and
have a programmatic way to change specific fields required for the test cases.
This could be done in such a way that the setup phase for all test cases that
wants to use murmur3 would define the partitioner in the test case instead of
specifying a yaml file to use. But that seems like a larger work and should
probably be handled outside of this ticket.
{quote}
+1
> PagingTest failure on trunk
> ---
>
> Key: CASSANDRA-15088
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15088
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Marcus Olsson
>Assignee: Marcus Olsson
>Priority: Normal
> Fix For: 4.0
>
> Attachments: 15088-trunk.txt
>
>
> [Example failure|https://circleci.com/gh/emolsson/cassandra/19]
> {noformat}
> java.lang.RuntimeException: Unable to gossip with any peers
> at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1546)
> at
> org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:553)
> at
> org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:841)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:699)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:650)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:379)
> at
> org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:501)
> at
> org.apache.cassandra.service.EmbeddedCassandraService.start(EmbeddedCassandraService.java:50)
> at org.apache.cassandra.cql3.PagingTest.setup(PagingTest.java:63)
> {noformat}
> Running the test case by itself won't reproduce the issue:
> {noformat}
> ant test -Dtest.name=PagingTest
> {noformat}
> But running it in parallel with other tests will:
> {noformat}
> ant test -Dtest.name=cql3/*
> {noformat}
> From the logs the following can be observed:
> {noformat}
> INFO [main] 2019-04-11 15:32:29,916 Node
> configuration:[...seed_provider=org.apache.cassandra.locator.SimpleSeedProvider{seeds=127.0.0.1:7017};
> storage_port=7027]
> ...
> DEBUG [main] 2019-04-17 10:11:55,418 connection attempt 0 to 127.0.0.1:7044
> (GOSSIP)
> DEBUG [main] 2019-04-17 10:11:55,420 creating outbound bootstrap to peer
> 127.0.0.1:7044, compression: false, encryption: disabled, coalesce: DISABLED,
> protocolVersion: 12
> DEBUG [ScheduledFastTasks:1] 2019-04-17 10:11:55,538 connection attempt 1 to
> 127.0.0.1:7044 (GOSSIP)
> DEBUG [ScheduledFastTasks:1] 2019-04-17 10:11:55,538 creating outbound
> bootstrap to peer 127.0.0.1:7044, compression: false, encryption: disabled,
> coalesce: DISABLED, protocolVersion: 12
> {noformat}
> It seems like we have an offset issue of 10 between seed/storage_port.
> The port 7044 does not seem to be defined anywhere though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15088) PagingTest failure on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-15088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831556#comment-16831556
]
Marcus Olsson commented on CASSANDRA-15088:
---
Thanks for looking at it. Yes, the port was actually added later to
cassandra-murmur.yaml during CASSANDRA-14956 as
[27b3579|https://github.com/apache/cassandra/commit/27b35799a46dd5b649c4a172f4f8316b48615304]
due to a test case failing in a similar way as described in this ticket. It
seems like the port was removed again by a later merge from 3.11 -> trunk.
I can fix a patch that aligns the fields but I'm not sure that it's worth to do
it for all fields (as long as the test cases are working as intended). Some
test cases i.e. _test/unit/org/apache/cassandra/cql3/PstmtPersistenceTest.java_
uses the parameter _prepared_statements_cache_size_mb: 1_ from cassandra.yaml
which I don't believe is necessary for test cases using cassandra-murmur.yaml
(currently at least). To try to keep these two files aligned will probably be
hard to remember as they have already diverged. We could of course add a
comment in the yaml files saying that the fields should be aligned but that can
still be missed.
But instead of keeping the two yaml files aligned perhaps a better approach
would be to have only one yaml file that all test cases depend on and have a
programmatic way to change specific fields required for the test cases. This
could be done in such a way that the setup phase for all test cases that wants
to use murmur3 would define the partitioner in the test case instead of
specifying a yaml file to use. But that seems like a larger work and should
probably be handled outside of this ticket.
> PagingTest failure on trunk
> ---
>
> Key: CASSANDRA-15088
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15088
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Marcus Olsson
>Assignee: Marcus Olsson
>Priority: Normal
> Fix For: 4.0
>
> Attachments: 15088-trunk.txt
>
>
> [Example failure|https://circleci.com/gh/emolsson/cassandra/19]
> {noformat}
> java.lang.RuntimeException: Unable to gossip with any peers
> at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1546)
> at
> org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:553)
> at
> org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:841)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:699)
> at
> org.apache.cassandra.service.StorageService.initServer(StorageService.java:650)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:379)
> at
> org.apache.cassandra.service.CassandraDaemon.init(CassandraDaemon.java:501)
> at
> org.apache.cassandra.service.EmbeddedCassandraService.start(EmbeddedCassandraService.java:50)
> at org.apache.cassandra.cql3.PagingTest.setup(PagingTest.java:63)
> {noformat}
> Running the test case by itself won't reproduce the issue:
> {noformat}
> ant test -Dtest.name=PagingTest
> {noformat}
> But running it in parallel with other tests will:
> {noformat}
> ant test -Dtest.name=cql3/*
> {noformat}
> From the logs the following can be observed:
> {noformat}
> INFO [main] 2019-04-11 15:32:29,916 Node
> configuration:[...seed_provider=org.apache.cassandra.locator.SimpleSeedProvider{seeds=127.0.0.1:7017};
> storage_port=7027]
> ...
> DEBUG [main] 2019-04-17 10:11:55,418 connection attempt 0 to 127.0.0.1:7044
> (GOSSIP)
> DEBUG [main] 2019-04-17 10:11:55,420 creating outbound bootstrap to peer
> 127.0.0.1:7044, compression: false, encryption: disabled, coalesce: DISABLED,
> protocolVersion: 12
> DEBUG [ScheduledFastTasks:1] 2019-04-17 10:11:55,538 connection attempt 1 to
> 127.0.0.1:7044 (GOSSIP)
> DEBUG [ScheduledFastTasks:1] 2019-04-17 10:11:55,538 creating outbound
> bootstrap to peer 127.0.0.1:7044, compression: false, encryption: disabled,
> coalesce: DISABLED, protocolVersion: 12
> {noformat}
> It seems like we have an offset issue of 10 between seed/storage_port.
> The port 7044 does not seem to be defined anywhere though.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
