Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 15 Oct 2013 14:12:44 +0000 (UTC)
From: "Jason Brown (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12671638.1380653161716.66109.1381846364466@arcas>
In-Reply-To: <JIRA.12671638.1380653161716@arcas>
References: <JIRA.12671638.1380653161716@arcas>
Subject: [jira] [Commented] (CASSANDRA-6124) Ability to specify a DC to
 consume from when using ColumnFamilyInputFormat externally
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jason Brown commented on CASSANDRA-6124:
----------------------------------------

It is starting to look like LOCAL_ONE is useful. We have some internal users that we startled to realize that once we opened up a second datacenter, that their 99%ile was not as as consistent as before. I do have an alternate solution to that in my back pocket ... but +1 to building in a CL.LOCAL_ONE 

> Ability to specify a DC to consume from when using ColumnFamilyInputFormat externally
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6124
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6124
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Hadoop
>            Reporter: Patricio Echague
>            Priority: Minor
>              Labels: hadoop
>             Fix For: 1.2.12
>
>         Attachments: CASSANDRA-6124.diff, CASSANDRA-6124-v2.diff
>
>
> Our production environment looks like this:
> - 6 cassandra nodes (online DC)
> - 3 cassandra nodes (offline DC)
> - Hadoop cluster.
> we are interested in connecting to the offline DC from hadoop (not colocated with cassandra offline dc)
> I've tested this patch and seems to work with our 1.2.5 deployment.
> Kindly review.


--
This message was sent by Atlassian JIRA
(v6.1#6144)