[
https://issues.apache.org/jira/browse/CASSANDRA-19001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791845#comment-17791845
]
Ekaterina Dimitrova commented on CASSANDRA-19001:
-------------------------------------------------
Thanks, [~paulo], appreciate it!
In the meantime I looked into the CI run in more detail:
- test_bootstrap_and_cleanup - this seems to need investigation; seems to have
been seen recently - CASSANDRA-18660. Actually in the other ticket the wait
time for the message was 120 seconds, here we see it being 90. I do not believe
this is related to what we do here, but seems worth it to open ticket and
investigate.
- test_decommissioned_wiped_node_can_join and
test_shutdown_wiped_node_cannot_join failed with similar errors. And they also
do not seem as something that could be triggered by this patch. I will open
tickets and bisect.
{code:java}
<class 'AssertionError'>
assert [Row(key=b'PP...e9\xbb'), ...] == [Row(key=b'5O...eL\xb6'), ...]
At index 0 diff: Row(key=b'PP9O0M9170',
C0=b'|\xa4\xc7\xb99\xd4\xae*\x85\x8c\xb3T\xa6!\x15\xaa{u\x90Rz\xc7J\x9a\xdd\x97b\xdd-\x07|\x06*\x06',
C1=b"\x95g\x0f\xa2\x13Bha\xefW'\xf9\x
{code}
- test_move_single_node - seems unrelated and deserving a ticket:
{code:java}
failed on teardown with "Failed: Unexpected error found in node logs (see
stdout for full details). Errors: [[node1] 'ERROR [main] 2023-11-30
00:02:24,154 CassandraDaemon.java:877 - Fatal configuration
error\norg.apache.cassandra.exceptions.ConfigurationException: Bootstrapping to
existing token 0 is not allowed (decommission/removenode the old node
first).\n\tat
org.apache.cassandra.dht.BootStrapper.getSpecifiedTokens(BootStrapper.java:199)\n\tat
org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:167)\n\tat
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1256)\n\tat
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1209)\n\tat
org.apache.cassandra.service.StorageService.initServer(StorageService.java:988)\n\tat
org.apache.cassandra.service.StorageService.initServer(StorageService.java:905)\n\tat
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:377)\n\tat
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:721)\n\tat
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:855)']"
Unexpected error found in node logs (see stdout for full details). Errors:
[[node1] 'ERROR [main] 2023-11-30 00:02:24,154 CassandraDaemon.java:877 - Fatal
configuration error\norg.apache.cassandra.exceptions.ConfigurationException:
Bootstrapping to existing token 0 is not allowed (decommission/removenode the
old node first).\n\tat
org.apache.cassandra.dht.BootStrapper.getSpecifiedTokens(BootStrapper.java:199)\n\tat
org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:167)\n\tat
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1256)\n\tat
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:1209)\n\tat
org.apache.cassandra.service.StorageService.initServer(StorageService.java:988)\n\tat
org.apache.cassandra.service.StorageService.initServer(StorageService.java:905)\n\tat
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:377)\n\tat
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:721)\n\tat
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:855)']
{code}
- test_expiration_overflow_policy_cap_default_ttl - unrelated, seems to deserve
a ticket, CC [~Bereng], might be interested into the error we see (there is
more in the logs of course, but this is outstanding to me):
{code:java}
> raise self._final_exception
E cassandra.InvalidRequest: Error from server: code=2200 [Invalid
query] message="Request on table ks.ttl_table with default ttl of 630720000
seconds exceeds maximum supported expiration date of 2038-01-19T03:14:06+00:00.
In order to avoid this use a lower TTL, change the expiration date overflow
policy or upgrade to a version where this limitation is fixed. See
CASSANDRA-14092 and CASSANDRA-14227 for more details."
{code}
The rest seem to be either OS errors or timeouts. On rebase at the end I will
run new full CI before commit and it will be confirmed
> Check whether the startup warnings for unknown modules represent a legit
> problem or cosmetic issue
> --------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19001
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19001
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 5.0-rc, 5.0.x, 5.x
>
>
> During the 5.0 alpha 2 release
> [vote|https://lists.apache.org/thread/lt3x0obr5cpbcydf5490pj6b2q0mz5zr],
> [~paulo] raised the following concerns:
> {code:java}
> Launched a tarball-based 5.0-alpha2 container on top of
> "eclipse-temurin:17-jre-focal" and the server starts up fine, can run
> nodetool and cqlsh.
> I got these seemingly harmless JDK17 warnings during startup and when
> running nodetool (no warnings on JDK11):
> WARNING: Unknown module: jdk.attach specified to --add-exports
> WARNING: Unknown module: jdk.compiler specified to --add-exports
> WARNING: Unknown module: jdk.compiler specified to --add-opens
> WARNING: A terminally deprecated method in java.lang.System has been called
> WARNING: System::setSecurityManager has been called by
> org.apache.cassandra.security.ThreadAwareSecurityManager
> (file:/opt/cassandra/lib/apache-cassandra-5.0-alpha2-SNAPSHOT.jar)
> WARNING: Please consider reporting this to the maintainers of
> org.apache.cassandra.security.ThreadAwareSecurityManager
> WARNING: System::setSecurityManager will be removed in a future release
> Anybody knows if these warnings are legit/expected ? We can create
> follow-up tickets if needed.
> $ java --version
> openjdk 17.0.9 2023-10-17
> OpenJDK Runtime Environment Temurin-17.0.9+9 (build 17.0.9+9)
> OpenJDK 64-Bit Server VM Temurin-17.0.9+9 (build 17.0.9+9, mixed mode,
> sharing)
> {code}
> {code:java}
> Clarification: - When running nodetool only the "Unknown module" warnings
> show up. All warnings show up during startup.{code}
> We need to verify whether this presents a real problem in the features where
> those modules are expected to be used, or if it is a false alarm.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
