[jira] [Commented] (CASSANDRA-16295) upgradesstables/scrub support for 2.x sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-16295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17304938#comment-17304938
]
Ekaterina Dimitrova commented on CASSANDRA-16295:
-
Thank you all, closing it
> upgradesstables/scrub support for 2.x sstables
> --
>
> Key: CASSANDRA-16295
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16295
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Ekaterina Dimitrova
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 3.11.x, 4.0-rc
>
>
> This support is important for 2.0/3.0 cluster or 3.0/4.0 cluster that
> can/might contain 2.x sstables.
> 4.0 supports versions down to {{ma}}, and 3.0 supports versions down to
> {{jb}} (3.0 and 2.0.1 correspondingly). So by the time you're on 4.0, you
> should have no 2.0 sstables either way, and this needs to be fixed for 3.11
>
> *NOTE: I just marked the ticket with both 3.11 and 4.0 rc versions even if
> the bug is presented only in 3.11 but to make it appear as a blocker on the
> 4.0 board!!*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16295) upgradesstables/scrub support for 2.x sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-16295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17304931#comment-17304931
]
Andres de la Peña commented on CASSANDRA-16295:
---
I haven't seen anything making it to fail, so I agree to just close it.
> upgradesstables/scrub support for 2.x sstables
> --
>
> Key: CASSANDRA-16295
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16295
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Ekaterina Dimitrova
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 3.11.x, 4.0-rc
>
>
> This support is important for 2.0/3.0 cluster or 3.0/4.0 cluster that
> can/might contain 2.x sstables.
> 4.0 supports versions down to {{ma}}, and 3.0 supports versions down to
> {{jb}} (3.0 and 2.0.1 correspondingly). So by the time you're on 4.0, you
> should have no 2.0 sstables either way, and this needs to be fixed for 3.11
>
> *NOTE: I just marked the ticket with both 3.11 and 4.0 rc versions even if
> the bug is presented only in 3.11 but to make it appear as a blocker on the
> 4.0 board!!*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16295) upgradesstables/scrub support for 2.x sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-16295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17304929#comment-17304929
]
Alex Petrov commented on CASSANDRA-16295:
-
I agree with your assessment of the situation [~e.dimitrova], there's no
confusion. I also agree we can close the ticket since there's no issue here.
> upgradesstables/scrub support for 2.x sstables
> --
>
> Key: CASSANDRA-16295
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16295
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Ekaterina Dimitrova
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 3.11.x, 4.0-rc
>
>
> This support is important for 2.0/3.0 cluster or 3.0/4.0 cluster that
> can/might contain 2.x sstables.
> 4.0 supports versions down to {{ma}}, and 3.0 supports versions down to
> {{jb}} (3.0 and 2.0.1 correspondingly). So by the time you're on 4.0, you
> should have no 2.0 sstables either way, and this needs to be fixed for 3.11
>
> *NOTE: I just marked the ticket with both 3.11 and 4.0 rc versions even if
> the bug is presented only in 3.11 but to make it appear as a blocker on the
> 4.0 board!!*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16295) upgradesstables/scrub support for 2.x sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-16295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17304520#comment-17304520
]
Ekaterina Dimitrova commented on CASSANDRA-16295:
-
Hi [~cscotta], there was a confusion in another ticket that upgradesstables is
broken in 3.11 and can't upgrade the old sstables which are not readable in
4.0. As a consequence, this can be an issue in a mixed version cluster. From
that perspective, it was agreed this issue to be handled before 4.0
As I took over CASSANDRA-15897 and did the testing I didn't see any issues with
upgradesstables.
To me it looked like a confusion due to test broken for different reasons.
Maybe [~adelapena], [~marcuse] or [~ifesdjeen] have something else in mind?
> upgradesstables/scrub support for 2.x sstables
> --
>
> Key: CASSANDRA-16295
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16295
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Ekaterina Dimitrova
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 3.11.x, 4.0-rc
>
>
> This support is important for 2.0/3.0 cluster or 3.0/4.0 cluster that
> can/might contain 2.x sstables.
> 4.0 supports versions down to {{ma}}, and 3.0 supports versions down to
> {{jb}} (3.0 and 2.0.1 correspondingly). So by the time you're on 4.0, you
> should have no 2.0 sstables either way, and this needs to be fixed for 3.11
>
> *NOTE: I just marked the ticket with both 3.11 and 4.0 rc versions even if
> the bug is presented only in 3.11 but to make it appear as a blocker on the
> 4.0 board!!*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16295) upgradesstables/scrub support for 2.x sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-16295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17304500#comment-17304500
]
C. Scott Andreas commented on CASSANDRA-16295:
--
[~e.dimitrova] I'm not sure I follow; could you say more about why this is a
4.0 blocker?
Users would need to run upgradesstables on 3.x after upgrading from 2.x (which
is expected). Let me know what more is needed here.
> upgradesstables/scrub support for 2.x sstables
> --
>
> Key: CASSANDRA-16295
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16295
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Ekaterina Dimitrova
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 3.11.x, 4.0-rc
>
>
> This support is important for 2.0/3.0 cluster or 3.0/4.0 cluster that
> can/might contain 2.x sstables.
> 4.0 supports versions down to {{ma}}, and 3.0 supports versions down to
> {{jb}} (3.0 and 2.0.1 correspondingly). So by the time you're on 4.0, you
> should have no 2.0 sstables either way, and this needs to be fixed for 3.11
>
> *NOTE: I just marked the ticket with both 3.11 and 4.0 rc versions even if
> the bug is presented only in 3.11 but to make it appear as a blocker on the
> 4.0 board!!*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16295) upgradesstables/scrub support for 2.x sstables
[
https://issues.apache.org/jira/browse/CASSANDRA-16295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17298246#comment-17298246
]
Ekaterina Dimitrova commented on CASSANDRA-16295:
-
I feel there was a chain of confusion because of a test failure which turned a
different issue.
At least with upgradesstables, I didn't find any issues on 3.0 or 3.11 during
the testing of CASSANDRA-15897
> upgradesstables/scrub support for 2.x sstables
> --
>
> Key: CASSANDRA-16295
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16295
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
>Reporter: Ekaterina Dimitrova
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 3.11.x, 4.0-rc
>
>
> This support is important for 2.0/3.0 cluster or 3.0/4.0 cluster that
> can/might contain 2.x sstables.
> 4.0 supports versions down to {{ma}}, and 3.0 supports versions down to
> {{jb}} (3.0 and 2.0.1 correspondingly). So by the time you're on 4.0, you
> should have no 2.0 sstables either way, and this needs to be fixed for 3.11
>
> *NOTE: I just marked the ticket with both 3.11 and 4.0 rc versions even if
> the bug is presented only in 3.11 but to make it appear as a blocker on the
> 4.0 board!!*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
