cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CASSANDRA-492) Data Center Quorum
Date Thu, 22 Oct 2009 17:18:59 GMT

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

Jonathan Ellis edited comment on CASSANDRA-492 at 10/22/09 5:17 PM:
--------------------------------------------------------------------

it is hard to see what is going on in the dcaware patch since there is so much reformatting
of existing code going on.  please resubmit without touching existing lines that doesn't actually
need to be changed.  (also, be aware of http://wiki.apache.org/cassandra/CodeStyle.)

      was (Author: jbellis):
    it is hard to see what is going on in the dcaware patch since there is so much reformatting
going on.  please resubmit without touching existing lines that doesn't actually need to be
changed.  (also, be aware of http://wiki.apache.org/cassandra/CodeStyle.)
  
> Data Center Quorum
> ------------------
>
>                 Key: CASSANDRA-492
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-492
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 0.5
>         Environment: Cassandra Core Code
>            Reporter: Vijay
>            Priority: Minor
>             Fix For: 0.5
>
>         Attachments: cassandra-DCAWARE.patch, DC-Config.xml
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Need a Cassandra Datacenter Quorum Read and Datacenter Quorum Write.
> Add 1 new enum DC_Quorum. basically reads with this will not span across the datacenter
it will use the existing nodes in the Datacenter which has this data and read from it.
> For writes - All the data centers need to get this data, (datac enters will be configured
in the storage-config.xml and number of replicas in it). Once configured write will basically
write to all the nodes in all the datacenter but will wait only for the write in the current
datacenter. 
> Example: We have 3 Datacenter A,B,C A has a replication factor of 3, B has 2 and C has
2. DC_Quorum write will make sure to write on 2 of 3 nodes in A.... B and C (total 4 +1) nodes
will be eventually consistent.
> Changes will be in RackAware, storage, read and write classes.
> Thanks
> Vijay

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