[
https://issues.apache.org/jira/browse/CASSANDRA-19697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855114#comment-17855114
]
Caleb Rackliffe commented on CASSANDRA-19697:
---------------------------------------------
{{shutdownClientServers()}} looks like it only affects drain and decom, so I
have no problem w/ the patch, and all it seems to do is revert to pre
CASSANDRA-19534 behavior. It doesn't matter on 4.1, as that doesn't wait for
the {{Dispatcher}} anyway. I'm just not entirely sure why 5.0 isn't getting
into a state where {{Dispatcher#requestExecutor}} is finished.
CC [~ifesdjeen]
> 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
>
> Attachments: shutdown_stuck.txt
>
>
> 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
