cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4561) update column family fails
Date Fri, 07 Sep 2012 09:25:08 GMT

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

Pavel Yaskevich commented on CASSANDRA-4561:
--------------------------------------------

Interesting, why does it try to merge remote schema if all of your nodes are in agreement,
can you run in debug mode as attach the log? The thing is timestamps are fixed long before
the storage server is initialized and the process involves truncate of the system.schema_*
CFs so I don't see any other reason why your schema still has old timestamps except some other
node sent it migration request... 

NPE that you experience is also interesting, cfMetaData() is always not null as CFs are copied
from one map to another on KS initialization, and KS itself could not be null or you would
have the assertion error instead of NPE.
                
> update column family fails
> --------------------------
>
>                 Key: CASSANDRA-4561
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4561
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4
>            Reporter: Zenek Kraweznik
>            Assignee: Pavel Yaskevich
>             Fix For: 1.1.5
>
>         Attachments: CASSANDRA-4561.patch
>
>
> [default@test] show schema;
> create column family Messages
>   with column_type = 'Standard'
>   and comparator = 'AsciiType'
>   and default_validation_class = 'BytesType'
>   and key_validation_class = 'AsciiType'
>   and read_repair_chance = 0.1
>   and dclocal_read_repair_chance = 0.0
>   and gc_grace = 864000
>   and min_compaction_threshold = 2
>   and max_compaction_threshold = 4
>   and replicate_on_write = true
>   and compaction_strategy = 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy'
>   and caching = 'KEYS_ONLY'
>   and compaction_strategy_options = {'sstable_size_in_mb' : '1024'}
>   and compression_options = {'chunk_length_kb' : '64', 'sstable_compression' : 'org.apache.cassandra.io.compress.DeflateCompressor'};
> [default@test] update column family Messages with min_compaction_threshold = 4 and  max_compaction_threshold
= 32;
> a5b7544e-1ef5-3bfd-8770-c09594e37ec2
> Waiting for schema agreement...
> ... schemas agree across the cluster
> [default@test] show schema;
> create column family Messages
>   with column_type = 'Standard'
>   and comparator = 'AsciiType'
>   and default_validation_class = 'BytesType'
>   and key_validation_class = 'AsciiType'
>   and read_repair_chance = 0.1
>   and dclocal_read_repair_chance = 0.0
>   and gc_grace = 864000
>   and min_compaction_threshold = 2
>   and max_compaction_threshold = 4
>   and replicate_on_write = true
>   and compaction_strategy = 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy'
>   and caching = 'KEYS_ONLY'
>   and compaction_strategy_options = {'sstable_size_in_mb' : '1024'}
>   and compression_options = {'chunk_length_kb' : '64', 'sstable_compression' : 'org.apache.cassandra.io.compress.DeflateCompressor'};

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message