[ 
https://issues.apache.org/jira/browse/CASSANDRA-20627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107415#comment-18107415
 ] 

Brandon Williams edited comment on CASSANDRA-20627 at 8/24/26 2:16 PM:
-----------------------------------------------------------------------

No PR I can comment on but the first 'gently' needs to go to the 'gently' 
kwarg. ie, {{self.cluster.stop(gently) -> self.cluster.stop(gently=gently)}} 
otherwise it's overriding the 'wait' parameter.


was (Author: brandon.williams):
No PR I can comment on but the first 'genltly' needs to go to the 'gently' 
kwarg. ie, {{self.cluster.stop(gently) -> self.cluster.stop(gently=gently)}} 
otherwise it's overriding the 'wait' parameter.

> dtest stop_cluster gently failure handling
> ------------------------------------------
>
>                 Key: CASSANDRA-20627
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20627
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Test/dtest/python
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>
> Retry cluster stop after exception when first stopping 'gently'
> Cluster stop requests in cleanup_cluster are made with "gently=True" when 
> Jacoco code coverage is enabled to allow the jacoco agent to record results; 
> however, some tests leave nodes in a state where this type of shutdown does 
> not succeed, resulting in the test being marked failed regardless of its true 
> completion status.
> The proposed change will retry these stop requests with "gently=False" so 
> that the test completion status will not be altered due to shutdown not 
> completing.
> patch based off 
> https://github.com/datastax/cassandra-dtest/commit/499af0a0b06488e082334f643e9e80613b27937c



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to