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/05/25 21:17:00 UTC

[jira] [Comment Edited] (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=17542241#comment-17542241 ] 

Caleb Rackliffe edited comment on CASSANDRA-17648 at 5/25/22 9:16 PM:
----------------------------------------------------------------------

Given the large amount of conceptual overlap, I'd like to defer work on CASSANDRA-17663 for 3.x to this ticket as well.


was (Author: maedhroz):
Given that large amount of conceptual overlap, I'd like to defer work on CASSANDRA-17663 for 3.x to this ticket.

> 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.7#820007)

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