cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1353) commit log recovery is broken when the CL contains mutations to CFs that have been dropped
Date Tue, 03 Aug 2010 20:02:16 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895014#action_12895014
] 

Gary Dusbabek commented on CASSANDRA-1353:
------------------------------------------

Connected to the target VM, address: '127.0.0.1:49379', transport: 'socket'
 INFO 14:55:18,246 [main] Loading settings from /Users/gary.dusbabek/codes/apache/git-trunk/out/production/conf1/cassandra.yaml
DEBUG 14:55:18,658 [main] Syncing log with a period of 10000
 INFO 14:55:18,658 [main] DiskAccessMode 'auto' determined to be mmap, indexAccessMode is
mmap
DEBUG 14:55:18,683 [main] setting auto_bootstrap to true
DEBUG 14:55:18,913 [main] Starting CFS Statistics
DEBUG 14:55:18,939 [main] Starting CFS Schema
DEBUG 14:55:19,028 [main] Starting CFS Migrations
DEBUG 14:55:19,042 [main] Starting CFS LocationInfo
DEBUG 14:55:19,056 [main] Starting CFS HintsColumnFamily
 INFO 14:55:19,133 [main] Loading schema version b72d969e-9f37-11df-903b-e700f669bcfc
DEBUG 14:55:19,153 [main] collecting 0 of 2147483647: Avro/Schema:false:1368@1280864748965
DEBUG 14:55:19,154 [main] collecting 1 of 2147483647: Keyspace1:false:62@1280864748965
 WARN 14:55:19,600 [main] Schema definitions were defined both locally and in cassandra.yaml.
Definitions in cassandra.yaml were ignored.
 INFO 14:55:19,615 [main] Replaying /Users/gary.dusbabek/cass-configs/trunk/node1/commitlog/CommitLog-1280862145661.log,
/Users/gary.dusbabek/cass-configs/trunk/node1/commitlog/CommitLog-1280864632989.log, /Users/gary.dusbabek/cass-configs/trunk/node1/commitlog/CommitLog-1280864746190.log,
/Users/gary.dusbabek/cass-configs/trunk/node1/commitlog/CommitLog-1280864747315.log, /Users/gary.dusbabek/cass-configs/trunk/node1/commitlog/CommitLog-1280864748249.log,
/Users/gary.dusbabek/cass-configs/trunk/node1/commitlog/CommitLog-1280864748880.log, /Users/gary.dusbabek/cass-configs/trunk/node1/commitlog/CommitLog-1280864749601.log,
/Users/gary.dusbabek/cass-configs/trunk/node1/commitlog/CommitLog-1280864798401.log
DEBUG 14:55:19,642 [main] Replaying /Users/gary.dusbabek/cass-configs/trunk/node1/commitlog/CommitLog-1280862145661.log
starting at 276
DEBUG 14:55:19,642 [main] Reading mutation at 276
DEBUG 14:55:19,788 [main] replaying mutation for system.[B@7848fbc0: {ColumnFamily(LocationInfo
[B:false:1@1280862146155,])}
DEBUG 14:55:19,835 [main] Reading mutation at 424
DEBUG 14:55:19,836 [main] replaying mutation for system.[B@764d2b11: {ColumnFamily(LocationInfo
[

> commit log recovery is broken when the CL contains mutations to CFs that have been dropped
> ------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1353
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1353
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Gary Dusbabek
>            Assignee: Gary Dusbabek
>             Fix For: 0.7 beta 1
>
>
> This was working, so the fix should include a RecoveryManager test that checks for regressions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message