You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2020/05/14 08:40:00 UTC

[jira] [Commented] (IGNITE-11147) Re-balance cancellation occur by non-affected event

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

Ignite TC Bot commented on IGNITE-11147:
----------------------------------------

{panel:title=Branch: [pull/7428/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5304072&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Re-balance cancellation occur by non-affected event
> ---------------------------------------------------
>
>                 Key: IGNITE-11147
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11147
>             Project: Ignite
>          Issue Type: Test
>          Components: cache
>    Affects Versions: 2.7
>            Reporter: Sergey Antonov
>            Assignee: Vladislav Pyatkov
>            Priority: Critical
>             Fix For: 2.9
>
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
>
> Re-balance cancels by non-affected events, for examples:
> 1) joining non affinity node
> 2) stating snapshot
> 3) starting/stopping other cache
> Try to skip as more as possible events instead of cancellation.
> After solved several issues appearing during this testing, I decided to add specific property allowing on/off rebalance's optimization. (see {{IgniteSystemProperties#IGNITE_DISABLE_REBALANCING_CANCELLATION_OPTIMIZATION}} by default false).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)