You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Caleb Rackliffe (Jira)" <ji...@apache.org> on 2022/07/12 16:01:00 UTC

[jira] [Commented] (CASSANDRA-17648) Backport CASSANDRA-17466 and CASSANDRA-17663 to 3.0 and 3.11

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

Caleb Rackliffe commented on CASSANDRA-17648:
---------------------------------------------

This shouldn't need to worry about CASSANDRA-17740, but mentioning it here just in case.

> Backport CASSANDRA-17466 and CASSANDRA-17663 to 3.0 and 3.11
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-17648
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17648
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Consistency/Repair
>            Reporter: David Capwell
>            Assignee: Caleb Rackliffe
>            Priority: Normal
>             Fix For: 3.0.x, 3.11.x
>
>
> CASSANDRA-17466 was fixed in 4.0+ but not 3.x.  This bug would close SSTables leaving the cluster in a bad state and needing to be restarted in order to recover



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

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org