[
https://issues.apache.org/jira/browse/CASSANDRA-17985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-17985:
----------------------------------------
Test and Documentation Plan: new test + cci run
Status: Patch Available (was: Open)
4.0;
https://github.com/apache/cassandra/pull/1944
https://app.circleci.com/pipelines/github/krummas/cassandra/833/workflows/4213ed2e-4b62-400a-a9e9-e67e2b12f5bd
4.1;
https://github.com/apache/cassandra/pull/1945
https://app.circleci.com/pipelines/github/krummas/cassandra/834/workflows/67af09f6-685e-4c6e-a35e-a9c211135bef
trunk;
https://github.com/apache/cassandra/pull/1946
https://app.circleci.com/pipelines/github/krummas/cassandra/835/workflows/c9327dc4-afde-41c6-ae2c-74f80feca43d
> Handle timeouts when shutting down MessagingService
> ---------------------------------------------------
>
> Key: CASSANDRA-17985
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17985
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Startup and Shutdown
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 4.x
>
>
> Sometimes when shutting down messaging service during decommission we get a
> timeout exception, which leaves StorageService.operationMode in "LEAVING"
> instead of "DECOMMISSIONED"
> We should catch the exception, improve logging and increase the timeout
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
