[
https://issues.apache.org/jira/browse/CASSANDRA-15897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295299#comment-17295299
]
Ekaterina Dimitrova commented on CASSANDRA-15897:
-------------------------------------------------
While testing I found a small bug in the 4.0 patch, fixed [here |
https://github.com/ekaterinadimitrova2/cassandra/commit/dcbff670cc3569aaa10befdafa4294968cf8c3c6].
I found out there is some problem when running on mixed cluster 3/3.11 and 4.0
WIP [tests |
https://github.com/ekaterinadimitrova2/cassandra-dtest/commit/3e82370ce827d6a2587a991f8d73fb40e6d8b6c7]
showing the different use cases I was testing (no, I am not going to keep
those test names, this is WIP). The tests marked with suffix "fail" are the
problem ones.
If we have two nodes with old sstables on 3/3.11, upgrade the sstables on both
nodes, and only one node upgrade to 4.0, then the DROP COMPACT STORAGE doesn't
work, the request times out.
If we continue and upgrade also the second 3/3.11 node to 4.0 then DROP COMPACT
STORAGE works. I need to investigate further today. If anyone has any ideas or
was considering this issue in a way, please, let me know.
> Dropping compact storage with 2.1-sstables on disk make them unreadable
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-15897
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15897
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Marcus Eriksson
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0-beta
>
>
> Test reproducing:
> https://github.com/krummas/cassandra/commits/marcuse/dropcompactstorage
--
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
