Mailing-List: contact issues-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
Date: Wed, 29 Jul 2015 18:02:05 +0000 (UTC)
From: "Anton Vinogradov (JIRA)" <jira@apache.org>
To: issues@ignite.incubator.apache.org
Message-ID: <JIRA.12842587.1435936384000.321985.1438192925270@Atlassian.JIRA>
In-Reply-To: <JIRA.12842587.1435936384000@Atlassian.JIRA>
References: <JIRA.12842587.1435936384000@Atlassian.JIRA>
 <JIRA.12842587.1435936384917@arcas>
Subject: [jira] [Issue Comment Deleted] (IGNITE-1093) Rebalancing with
 default parameters is very slow
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Anton Vinogradov updated IGNITE-1093:
-------------------------------------
    Comment: was deleted

(was: I've created simple test to check how much time takes to relocated 40_000_000 entries:

{
Ignite ignite = startGrid(0);
      
try (IgniteDataStreamer<Integer, String> stmr = ignite.dataStreamer(CACHE_NAME_DHT)) {
	for (int i = 0; i < 40_000_000; i++) 
		stmr.addData(i, KEY_VAL);	
}

startGrid(1);      

stopAllGrids();
}

By default RebalanceTimeout equals to 10 seconds. In this case new node requests entries each 10-20 seconds. And old node creates and sends message with entries. Sounds bad, IMHO.
And in this case we have following metrics:

data load takes 81 s
suply message preparation takes 49 s
send-receive (from send to handle start) takes 399 s
put gained entries to cache takes 118 s

So, I set cacheCfg.setRebalanceTimeout(1000000) and gain:

data load takes 81s
suply message preparation takes 49 s
send-receive (from send to handle start) takes 45 s
put gained entries to cache takes 118 s

Seems that we have to change default value of rebalanceTimeout)

> Rebalancing with default parameters is very slow
> ------------------------------------------------
>
>                 Key: IGNITE-1093
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1093
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: sprint-7
>            Reporter: Pavel Konstantinov
>            Assignee: Anton Vinogradov
>            Priority: Critical
>             Fix For: sprint-8
>
>
> # Start one node with partitioned cache with one backup.
> # Load into the cache 40billions of keys using DataStreamer
> # Start second node on the same host


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)