You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2012/08/30 20:51:07 UTC

[jira] [Comment Edited] (CASSANDRA-4589) writes are allowed when RF>N

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

Brandon Williams edited comment on CASSANDRA-4589 at 8/31/12 5:49 AM:
----------------------------------------------------------------------

bq.  if we cannot Read or write to a KS why allow creating it?

Because that's how you add them for new DCs, with an rf of zero until you have the nodes in place.
                
      was (Author: brandon.williams):
    bq.  if we cannot Read or write to a KS why allow creating it?

Because that's how you add them for new DCs, and you might want to add this keyspace only to a new DC that hasn't bootstrapped in yet.
                  
> writes are allowed when RF>N
> ----------------------------
>
>                 Key: CASSANDRA-4589
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4589
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.2
>            Reporter: Brandon Williams
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> Easily repro'd by running stress with a ridiculous rf:
> # tools/bin/cassandra-stress -n 100000 -i 1 -o insert -l123456
> We're supposed to allow creation of a ks where the rf exceeds the amount of nodes, but we shouldn't be able to write to it.

--
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