ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Vinogradov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1093) Rebalancing with default parameters is very slow
Date Thu, 13 Aug 2015 08:04:45 GMT

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

Anton Vinogradov commented on IGNITE-1093:
------------------------------------------

Working on Yardstick benchmark to analize difference between old and new implementation.
Going to start 3 server nodes and one client and make put-remove requests as many as possible.
Each, for example, 30 seconds going to start and then stop one server node to have permanent
rebalancing. 
This should shows system degradation during rebalancing.
One more test is to start 2 + 1 node and to detect how long takes to start one more server
node in SYNC rebalancing mode.
Also, current status is: I have only one test failing at rebalancing suite, going to fix this
after benchmarking.
Backward compatibility also an issue and should be done as final part of this refactoring.

> 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: ignite-1.4
>
>
> # 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)

Mime
View raw message