cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Thompson (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-10933) failing
Date Wed, 23 Dec 2015 17:44:47 GMT
Philip Thompson created CASSANDRA-10933:

             Summary: failing
                 Key: CASSANDRA-10933
             Project: Cassandra
          Issue Type: Sub-task
            Reporter: Philip Thompson
             Fix For: 3.0.x, 3.x
         Attachments: node1.log is failing on HEAD for cassandra-3.0. The test upgrades from
2.1.3 to 3.0, and checks the following behavior

# on startup, it should detect that the old-format sstable had its
# index summary downsampled (forcing it to be rebuilt)
node.watch_log_for("Detected erroneously downsampled index summary")

However, this is not happening. The node's log is attached. It is quite possible that the
"fix" here is that we only want to test upgrading from 2.1.3 to 2.1.LATEST, but that's not
for me to decide. I can easily implement that, if that happens to be the case.

This message was sent by Atlassian JIRA

View raw message