You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/06/22 18:41:56 UTC
[jira] Created: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
0.7 cannot read 0.6 system table
--------------------------------
Key: CASSANDRA-1218
URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.7
Reporter: Jonathan Ellis
Assignee: Gary Dusbabek
Priority: Critical
Fix For: 0.7
to reproduce:
start w/ empty data, commitlog
start 0.6
kill it when it completes starting
r/m commitlog (should have LocationInfo sstables already)
start 0.7
ERROR 12:39:18,593 Fatal exception during initialization
org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1218:
-------------------------------------
Attachment: 0001-CFS-should-ignore-non-db-files.patch
0002-use-diskformat-when-recreating-rowkey-bloom-filter.patch
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-diskformat-when-recreating-rowkey-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882136#action_12882136 ]
Gary Dusbabek commented on CASSANDRA-1218:
------------------------------------------
Stu tried explaining to me yesterday, but I wasn't really getting it.
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-disk-format-when-recreating-bloom-filter.patch, 0002-use-raw-key-when-recreating-or-writing-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881811#action_12881811 ]
Stu Hood commented on CASSANDRA-1218:
-------------------------------------
+1
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-raw-key-when-recreating-or-writing-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882053#action_12882053 ]
Jonathan Ellis commented on CASSANDRA-1218:
-------------------------------------------
why can't we use the (shorter) raw key in the BF for RP, as long as we're consistent about doing that?
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-disk-format-when-recreating-bloom-filter.patch, 0002-use-raw-key-when-recreating-or-writing-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881781#action_12881781 ]
Jonathan Ellis commented on CASSANDRA-1218:
-------------------------------------------
Look for Descriptor.hasStringsInBloomFilter -- the idea is supposed to be that when loading an old sstable, we rebuild its BF using the raw byte key so we don't have to keep paying the convert-to-String price.
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-diskformat-when-recreating-rowkey-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1218:
-------------------------------------
Attachment: 0002-use-raw-key-when-recreating-or-writing-bloom-filter.patch
Alternate second patch that uses raw keys when recreating or writing bloom filters.
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-raw-key-when-recreating-or-writing-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881823#action_12881823 ]
Stu Hood commented on CASSANDRA-1218:
-------------------------------------
Ah shoot: 0002 won't work for RandomPartitioner... sorry for the shoddy review. I missed that it stopped writing the disk-format to disk: SSTableWriter still needs to write the results of convertToDiskFormat to disk.
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-raw-key-when-recreating-or-writing-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1218:
-------------------------------------
Attachment: (was: 0002-use-diskformat-when-recreating-rowkey-bloom-filter.patch)
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-raw-key-when-recreating-or-writing-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Dusbabek updated CASSANDRA-1218:
-------------------------------------
Attachment: 0002-use-disk-format-when-recreating-bloom-filter.patch
Use disk formatted key when recreating bloom filter.
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-disk-format-when-recreating-bloom-filter.patch, 0002-use-raw-key-when-recreating-or-writing-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881779#action_12881779 ]
Stu Hood commented on CASSANDRA-1218:
-------------------------------------
Rather than using the disk format in the bloom filter, we should probably use the plain key.
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-diskformat-when-recreating-rowkey-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stu Hood reopened CASSANDRA-1218:
---------------------------------
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-raw-key-when-recreating-or-writing-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stu Hood updated CASSANDRA-1218:
--------------------------------
Attachment: 0002-keys-in-bloom-disk-keys-on-disk.patch
Patch to always use byte[] keys in the bloom filter, and convertToDisk encoded keys on disk.
Sorry for all the confusion!
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-keys-in-bloom-disk-keys-on-disk.patch, 0002-use-disk-format-when-recreating-bloom-filter.patch, 0002-use-raw-key-when-recreating-or-writing-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881805#action_12881805 ]
Gary Dusbabek commented on CASSANDRA-1218:
------------------------------------------
My original intent was to keep things similar to 0.6, but Jonathans comment made me realize there was little point--let's just use raw keys throughout.
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-raw-key-when-recreating-or-writing-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CASSANDRA-1218) 0.7 cannot read 0.6 system table
Posted by "Stu Hood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881796#action_12881796 ]
Stu Hood commented on CASSANDRA-1218:
-------------------------------------
Gary's patch is correct, in that it makes the filter rebuilding match up with the rest of the codebase (disk-formatted-bytes in the filter).
But rather than storing disk-formatted-bytes in the bloom filter, we should probably store the actual key bytes.
> 0.7 cannot read 0.6 system table
> --------------------------------
>
> Key: CASSANDRA-1218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1218
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Critical
> Fix For: 0.7
>
> Attachments: 0001-CFS-should-ignore-non-db-files.patch, 0002-use-diskformat-when-recreating-rowkey-bloom-filter.patch
>
>
> to reproduce:
> start w/ empty data, commitlog
> start 0.6
> kill it when it completes starting
> r/m commitlog (should have LocationInfo sstables already)
> start 0.7
> ERROR 12:39:18,593 Fatal exception during initialization
> org.apache.cassandra.config.ConfigurationException: Found system table files, but they couldn't be loaded. Did you change the partitioner?
> at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:153)
> at org.apache.cassandra.thrift.CassandraDaemon.setup(CassandraDaemon.java:93)
> at org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:90)
> at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:221)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.