[ https://issues.apache.org/jira/browse/CASSANDRA-19697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17854464#comment-17854464 ]
Brandon Williams commented on CASSANDRA-19697: ---------------------------------------------- The mysterious commonality that connects this back to CASSANDRA-19534 despite entirely different classes being targetted by byteman in 5.0 and trunk is that the JVM does not exit in either branch, where in 4.1 it shuts down gracefully. Here is where 5.0 and trunk stop: {quote} INFO [Native-Transport-Requests-1] 2024-06-12 10:02:16,679 Keyspace.java:379 - Creating replication strategy bar params KeyspaceParams{durable_writes=true, replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy, replication_factor=1}} INFO [StorageServiceShutdownHook] 2024-06-12 10:02:16,686 HintsService.java:234 - Paused hints dispatch {quote} but 4.1 continues: {quote} INFO [Native-Transport-Requests-1] 2024-06-12 09:59:04,474 Keyspace.java:394 - Creating replication strategy foo params KeyspaceParams{durable_writes=true, replication=ReplicationParams{class=org.apache.cassandra.locator.SimpleStrategy, replication_factor=1}} INFO [StorageServiceShutdownHook] 2024-06-12 09:59:04,481 HintsService.java:235 - Paused hints dispatch INFO [StorageServiceShutdownHook] 2024-06-12 09:59:04,483 Server.java:176 - Stop listening for CQL clients INFO [StorageServiceShutdownHook] 2024-06-12 09:59:04,484 Gossiper.java:2139 - Announcing shutdown INFO [StorageServiceShutdownHook] 2024-06-12 09:59:04,484 StorageService.java:3075 - Node localhost/127.0.0.1:7000 state jump to shutdown INFO [StorageServiceShutdownHook] 2024-06-12 09:59:04,485 StorageService.java:3075 - Node localhost/127.0.0.1:7000 state jump to shutdown INFO [StorageServiceShutdownHook] 2024-06-12 09:59:06,487 MessagingService.java:526 - Waiting for messaging service to quiesce ... {quote} In the thread dump I see some epoll threads still running, but I'm not sure if that's typical. I don't immediately see anything from CASSANDRA-19534 that would cause this, [~ifesdjeen] could you take a look? The [byteman script|https://github.com/apache/cassandra-dtest/blob/trunk/byteman/merge_schema_failure_4x.btm] is calling System.exit(0) inside Schema.merge. > Test failure: > materialized_views_test.py::TestMaterializedViews::test_rename_column_atomicity > --------------------------------------------------------------------------------------------- > > Key: CASSANDRA-19697 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19697 > Project: Cassandra > Issue Type: Bug > Components: Feature/Materialized Views > Reporter: Brandon Williams > Assignee: Brandon Williams > Priority: Normal > Fix For: 5.0-rc, 5.x > > > Breaking this out from CASSANDRA-19683. The byteman script fails to execute > in 5.0/trunk after CASSANDRA-19534. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org