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 3F82D10BAD for ; Wed, 20 Nov 2013 03:09:53 +0000 (UTC) Received: (qmail 91420 invoked by uid 500); 20 Nov 2013 03:09:39 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 91364 invoked by uid 500); 20 Nov 2013 03:09:30 -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 91297 invoked by uid 99); 20 Nov 2013 03:09:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Nov 2013 03:09:24 +0000 Date: Wed, 20 Nov 2013 03:09:23 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CASSANDRA-5237) Add consistency level EACH_ONCE 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-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-5237. --------------------------------------- Resolution: Won't Fix > Add consistency level EACH_ONCE > ------------------------------- > > Key: CASSANDRA-5237 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5237 > Project: Cassandra > Issue Type: Improvement > Reporter: Srdjan Mitrovic > Priority: Minor > > Use case: > If we have 2 datacenters and 2 replicas per datacenter a good fault tolerant consistency strategy would be to use level EACH_ONCE for writes as in that case it is fault tolerant even if 2 nodes die (one in each dc). If we assume that a node from local dc will always reply faster then remote dc we could use CL_TWO for reads and it would work fast for reads in normal conditions and be fault tolerant if a node or 2 nodes die. -- This message was sent by Atlassian JIRA (v6.1#6144)