Function test Cassandra Unit connection errors with Cassandra Server v3.x and JDK11. #1621
Comments
|
|
|
I also noticed this ( from Reptoro service but trying to query same
stage/dev Cassandra instance) in cases when interactions between service
and Cassandra was not done for some time interval greater then ~10 min. .
It seems like Cassandra connections must be "warm" up before trying to
query it?!
…On Tue, May 26, 2020 at 11:53 AM Jeremy Whiting ***@***.***> wrote:
I found this issue only happens when the jar artifacts have been
compiled/generated using JDK8.
Not certain this is a cause for concern. The workaround is to use JDK11 to
compile/generate everything.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1621 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALOAMGKJJZG3IAMLC5FVGBTRTOGP3ANCNFSM4M624AKA>
.
--
Gjorgji Georgievski
Senior Software Engineer
EXD Software Production - Middleware & Management
*ORG*:CXnO R&D DevOps;
*GEO*:49.2313561;16.5761589
*CELL*:+420608086176
*URL*:https://rover.redhat.com/people/profile/ggeorgie
Red Hat EMEA <https://www.redhat.com/>
*ADDRESS*: Purkyňova 111, 618 00 Brno-Královo Pole
*EMAIL*: [email protected]
*DESK:* M: +420-532-294-491
<https://www.redhat.com/>
|
Could be necessary yes. I don't know. It requires further testing. |
|
|
That stack trace from Netty is a bit misleading. It's not causing the issue you have, just reporting that some of Netty's "optimizations" aren't available when running under JDK 9+. See here for more: netty/netty#7769. I'm looking at the Driver ticket here and with a simple project that uses the driver to connect to Cassandra and execute a query, I see the same DEBUG log from Netty (when running with JDK11), but the connection and query are successful. I'm going through the combinations of compile/runtime JVMs and I hope to find the solution or fix soon. |
|
@emerkle826 If you need help configuring the Indy project to quickly execute an individual failing test do ask. |
|
Some more investigation about re-creating the issue. The default distribution has some influence here when running the ftests with Cassandra. The JAVA_HOME env variable is ignored when booting the failsafe tests. |
|
Bah, Cassandra 3.x is only compatible with jdk8. Cassandra 4.0 supports JDK11. This issue tracks the update. |
|
@whitingjr Sorry I haven't replied sooner. |
whitingjr
changed the title
|
I've filed an issue in our team to avoid Cassandra for local functional test runs, then use pre- and post- steps in our CI pipeline to manage keyspaces in a long-running Cassandra instance in our test environment. This should allow us to sidestep the issues with cassandra-unit. I don't think that issue made the cut for the current sprint, so I'm hoping to get it done in the next month or less. |
When running the Function Tests locally I am seeing Cassandra client connection errors. When Cassandra server is using JDK11.
In this example I am running the
RemoteRepoGetErrorTesttest.The knock on effect is the fixture server cannot instanciate the cacheProvider field. Which results in a NullPointerException.
The text was updated successfully, but these errors were encountered: