Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2854611F89 for ; Thu, 4 Sep 2014 11:12:52 +0000 (UTC) Received: (qmail 84632 invoked by uid 500); 4 Sep 2014 11:12:51 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 84592 invoked by uid 500); 4 Sep 2014 11:12:51 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 84580 invoked by uid 99); 4 Sep 2014 11:12:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Sep 2014 11:12:51 +0000 Date: Thu, 4 Sep 2014 11:12:51 +0000 (UTC) From: "Hari Sekhon (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-7877) Tunable consistency across datacenters - LOCAL_QUORUM + 1 other DC MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated CASSANDRA-7877: ----------------------------------- Summary: Tunable consistency across datacenters - LOCAL_QUORUM + 1 other DC (was: Tunable consistency across datacenters - LOCAL_QUORUM + 1 at other DC) > Tunable consistency across datacenters - LOCAL_QUORUM + 1 other DC > ------------------------------------------------------------------ > > Key: CASSANDRA-7877 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7877 > Project: Cassandra > Issue Type: Improvement > Reporter: Hari Sekhon > Priority: Minor > > Right now tunable consistency allows for things like local quorum and each quorum across multiple datacenters. > I propose something in between where you achieve local quorum + 1 node at other DC. This would make sure the data is written to the other datacenter for resilience purposes but be better performing that having to do an each quorum write at both datacenters. Mind you re-reviewing each_quorum I'm not sure how much more performant this would be... > EDIT: thinking about this more this is probably reasonably covered by each quorum given that by the time you write to 1 replica node in other DC you may as well write to 2 in which case each quorum is probably the way to go. > Although if you have 3 or more datacenters then perhaps there should be an option to do quorum in local DC + quorum in one other DC before confirming write to prevent data loss on site failure? -- This message was sent by Atlassian JIRA (v6.3.4#6332)