Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 29 Oct 2013 19:49:26 +0000 (UTC)
From: =?utf-8?Q?Piotr_Ko=C5=82aczkowski_=28JIRA=29?= <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12676474.1383076076396.1115.1383076166045@arcas>
In-Reply-To: <JIRA.12676474.1383076076396@arcas>
References: <JIRA.12676474.1383076076396@arcas>
Subject: [jira] [Updated] (CASSANDRA-6268) Poor performance of Hadoop if any
 DC is using VNodes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CASSANDRA-6268?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Ko=C5=82aczkowski updated CASSANDRA-6268:
------------------------------------------

    Attachment: 0001-DSP-2572-Adds-ability-to-set-target-DCs-where-a-Hado.p=
atch

> Poor performance of Hadoop if any DC is using VNodes
> ----------------------------------------------------
>
>                 Key: CASSANDRA-6268
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6268
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Hadoop
>            Reporter: Piotr Ko=C5=82aczkowski
>            Assignee: Piotr Ko=C5=82aczkowski
>         Attachments: 0001-DSP-2572-Adds-ability-to-set-target-DCs-where-a=
-Hado.patch
>
>
> Some customers are complaining about huge number of splits in Hadoop caus=
ed by VNodes. Disabling vnodes only in Hadoop DC does not fix it, because s=
plits are generated from the results of describe_ring, which returns a huge=
 number of ranges.=20
> The proposed fix:
> - allows for specifying the DCs the Hadoop job should be run
> - merges the consecutive ranges before generating Hadoop splits, so we do=
n't have artificial range splitting caused by vnodes in the other DCs


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