Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 12 May 2017 07:18:04 +0000 (UTC)
From: "Marcus Eriksson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12607152.1347408091000.195071.1494573484097@Atlassian.JIRA>
In-Reply-To: <JIRA.12607152.1347408091000@Atlassian.JIRA>
References: <JIRA.12607152.1347408091000@Atlassian.JIRA> <JIRA.12607152.1347408091104@jira-lw-us.apache.org>
Subject: [jira] [Updated] (CASSANDRA-4650) RangeStreamer should be smarter
 when picking endpoints for streaming in case of N >=3 in each DC.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 12 May 2017 07:18:09 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson updated CASSANDRA-4650:
---------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 4.x)
                   4.0
           Status: Resolved  (was: Patch Available)

+1, committed

psjava seems to be the first MIT-licensed library we use (ie, there are at least no MIT-licenses in lib/licenses/*), but it seems it is OK according to this: http://apache.org/legal/resolved.html#category-a

> RangeStreamer should be smarter when picking endpoints for streaming in case of N >=3 in each DC.  
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4650
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4650
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 1.1.5
>            Reporter: sankalp kohli
>            Assignee: sankalp kohli
>            Priority: Minor
>              Labels: streaming
>             Fix For: 4.0
>
>         Attachments: CASSANDRA-4650_trunk.txt, photo-1.JPG
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> getRangeFetchMap method in RangeStreamer should pick unique nodes to stream data from when number of replicas in each DC is three or more. 
> When N>=3 in a DC, there are two options for streaming a range. Consider an example of 4 nodes in one datacenter and replication factor of 3. 
> If a node goes down, it needs to recover 3 ranges of data. With current code, two nodes could get selected as it orders the node by proximity. 
> We ideally will want to select 3 nodes for streaming the data. We can do this by selecting unique nodes for each range.  
> Advantages:
> This will increase the performance of bootstrapping a node and will also put less pressure on nodes serving the data. 
> Note: This does not affect if N < 3 in each DC as then it streams data from only 2 nodes. 


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org