[
https://issues.apache.org/jira/browse/CASSANDRA-16425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296533#comment-17296533
]
Michael Semb Wever commented on CASSANDRA-16425:
------------------------------------------------
CI run when through above, as well.
{{testRecoverOverflowedExpirationWithSSTableScrub}} looks ok
[here|https://ci-cassandra.apache.org/job/Cassandra-devbranch/465/testReport/org.apache.cassandra.cql3.validation.operations/TTLTest/].
Of the 19 failures, most (like Adam writes) can be attributed to other tickets
and work. But it's a bit difficult to see clearly and there's a few that don't
make sense. Kicking off a new rebased CI to double check…
[!https://ci-cassandra.apache.org/job/Cassandra-devbranch/466/badge/icon!|https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/466/pipeline]
> Improve handling of repair sessions during startup/shutdown
> -----------------------------------------------------------
>
> Key: CASSANDRA-16425
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16425
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 4.0-beta
>
>
> We should send out a fail message on clean shutdown and if we find an ongoing
> repair session during startup we should fail it and tell participants.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
