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

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

{panel:title=Branch: [pull/8144/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8144/head] Base: [master] : New Tests 
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}MVCC PDS 4{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5771119]]
* {color:#013220}IgnitePdsMvccTestSuite4: 
NoUnnecessaryRebalancesTest.testNoRebalancesOnCacheCreation - PASSED{color}

{color:#00008b}PDS 4{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5771093]]
* {color:#013220}IgnitePdsTestSuite4: 
NoUnnecessaryRebalancesTest.testNoRebalancesOnCacheCreation - PASSED{color}

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5771132&buildTypeId=IgniteTests24Java8_RunAll]

> DynamicCacheChangeBatch invokes partition validation for all caches
> -------------------------------------------------------------------
>
>                 Key: IGNITE-13353
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13353
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Sergey Uttsel
>            Assignee: Sergey Uttsel
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Right now, DynamicCacheChangeBatch triggers partition validation for all 
> caches. It can (and most possibly it will) show inconsistency between 
> partitions in case of using DataStreamer. It will lead to the data rebalance, 
> while it's not needed - updates should be streamed to backup nodes after some 
> time due to asynchronous behavior of DataStramer
> In the attached log file cache was created at 1:33, it led to the partitions 
> evictions right after that and to the rebalance at ~2:36(they have 
> rebalanceDelay = 1hour). This behaviour led to these 2 drops almost to zero 
> in write operations:



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

Reply via email to