[
https://issues.apache.org/jira/browse/IGNITE-9928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684879#comment-16684879
]
Ignite TC Bot commented on IGNITE-9928:
---------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Queries{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2301468]]
* IgniteCacheMvccSqlTestSuite:
CacheMvccPartitionedSqlCoordinatorFailoverTest.testUpdate_N_Objects_ClientServer_Backups2_Sql
- 0,0% fails in last 100 master runs.
{color:#d04437}SPI{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2301449]]
* IgniteSpiTestSuite:
IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown2 - 0,0%
fails in last 100 master runs.
{color:#d04437}Queries 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2301517]]
* IgniteBinaryCacheQueryTestSuite:
IgniteSqlSplitterSelfTest.testReplicatedTablesUsingPartitionedCacheSegmentedClientRO
- 0,0% fails in last 100 master runs.
{color:#d04437}PDS 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2301507]]
* IgnitePdsTestSuite2:
ClientAffinityAssignmentWithBaselineTest.testPartitionedTxCache - 0,0% fails in
last 100 master runs.
{color:#d04437}Continuous Query 3{color} [[tests
5|https://ci.ignite.apache.org/viewLog.html?buildId=2301495]]
* IgniteCacheQuerySelfTestSuite5:
IgniteCacheContinuousQueryBackupQueueTest.testManyQueryBackupQueue - 0,0% fails
in last 100 master runs.
{color:#d04437}Hadoop{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2301433]]
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2301524&buildTypeId=IgniteTests24Java8_RunAll]
> MVCC TX: Late affinity assignment support.
> ------------------------------------------
>
> Key: IGNITE-9928
> URL: https://issues.apache.org/jira/browse/IGNITE-9928
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Roman Kondakov
> Assignee: Igor Seliverstov
> Priority: Major
> Fix For: 2.8
>
>
> On unstable topology SQL queries are mapped to random partitions in OWNED
> state (regardless whether it's going to be evicted or not) but updates take
> into consideration current ideal affinity assignment only (in other words
> updates are sent to current backups only and don't touch partitions which are
> going to be evicted) what causes a situation when subsequent reads may not
> see previous updates.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
