cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-13119) dtest failure upgrade_tests.upgrade_supercolumns_test.TestSCUpgrade.upgrade_super_columns_through_all_versions_test
Date Wed, 11 Jan 2017 21:58:16 GMT
Ariel Weisberg created CASSANDRA-13119:
------------------------------------------

             Summary: dtest failure upgrade_tests.upgrade_supercolumns_test.TestSCUpgrade.upgrade_super_columns_through_all_versions_test
                 Key: CASSANDRA-13119
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13119
             Project: Cassandra
          Issue Type: Bug
          Components: Core, Testing
            Reporter: Ariel Weisberg
            Assignee: Ariel Weisberg
            Priority: Critical
             Fix For: 3.0.x, 3.x, 4.x


The test complains about unreadable sstables version ka and lb during upgrade which is 2.1
and 2.2. These tables look like system tables not user tables.

I looked and I can't find any place where system tables are upgraded on upgrade. You can specify
them explicitly by name with nodetool, but nodetool defaults to only upgrading user tables
and doesn't have a flag to upgrade all tables.

These tables probably need to be removed if unused or upgraded if in use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message