[
https://issues.apache.org/jira/browse/IGNITE-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803843#comment-16803843
]
Ignite TC Bot commented on IGNITE-9913:
---------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC PDS 4{color} [[tests
7|https://ci.ignite.apache.org/viewLog.html?buildId=3442305]]
* IgnitePdsMvccTestSuite4:
IgnitePdsContinuousRestartTestWithSharedGroupAndIndexes.testRebalancingDuringLoad_1000_500_1_1
- 0,0% fails in last 394 master runs.
* IgnitePdsMvccTestSuite4:
IgnitePdsContinuousRestartTestWithSharedGroupAndIndexes.testRebalancingDuringLoad_1000_500_8_16
- 0,0% fails in last 394 master runs.
* IgnitePdsMvccTestSuite4:
IgnitePdsContinuousRestartTestWithSharedGroupAndIndexes.testRebalancingDuringLoad_8000_500_8_1
- 0,0% fails in last 394 master runs.
* IgnitePdsMvccTestSuite4:
IgnitePdsContinuousRestartTestWithSharedGroupAndIndexes.testRebalancingDuringLoad_8000_500_1_1
- 0,0% fails in last 394 master runs.
* IgnitePdsMvccTestSuite4:
IgnitePdsContinuousRestartTestWithSharedGroupAndIndexes.testRebalancingDuringLoad_1000_20000_1_1
- 0,0% fails in last 394 master runs.
* IgnitePdsMvccTestSuite4:
IgnitePdsContinuousRestartTestWithSharedGroupAndIndexes.testRebalancingDuringLoad_1000_20000_8_1
- 0,0% fails in last 394 master runs.
{color:#d04437}MVCC PDS 3{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=3394663]]
* IgnitePdsMvccTestSuite3:
IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_1000_500_1_1 - 0,0%
fails in last 399 master runs.
* IgnitePdsMvccTestSuite3:
IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_1000_20000_8_1 - 0,0%
fails in last 399 master runs.
* IgnitePdsMvccTestSuite3:
IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_1000_20000_1_1 - 0,0%
fails in last 399 master runs.
* IgnitePdsMvccTestSuite3:
IgnitePdsContinuousRestartTest.testRebalancingDuringLoad_1000_20000_8_16 - 0,0%
fails in last 399 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3383266&buildTypeId=IgniteTests24Java8_RunAll]
> Prevent data updates blocking in case of backup BLT server node leave
> ---------------------------------------------------------------------
>
> Key: IGNITE-9913
> URL: https://issues.apache.org/jira/browse/IGNITE-9913
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Reporter: Ivan Rakov
> Assignee: Amelchev Nikita
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ignite cluster performs distributed partition map exchange when any server
> node leaves or joins the topology.
> Distributed PME blocks all updates and may take a long time. If all
> partitions are assigned according to the baseline topology and server node
> leaves, there's no actual need to perform distributed PME: every cluster node
> is able to recalculate new affinity assigments and partition states locally.
> If we'll implement such lightweight PME and handle mapping and lock requests
> on new topology version correctly, updates won't be stopped (except updates
> of partitions that lost their primary copy).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
