ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9928) MVCC TX: Late affinity assignment support.
Date Mon, 12 Nov 2018 15:23:00 GMT

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

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

{panel:title=Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Queries{color} [[tests 4|https://ci.ignite.apache.org/viewLog.html?buildId=2210231]]
* IgniteCacheMvccSqlTestSuite: CacheMvccContinuousWithTransformerPartitionedSelfTest.testContinuousWithTransformerKeepBinaryAsync
- 0,0% fails in last 100 master runs.
* IgniteCacheMvccSqlTestSuite: CacheMvccReplicatedSqlQueriesTest.testAccountsTxSql_ClientServer_Backups2
- 0,0% fails in last 100 master runs.
* IgniteCacheMvccSqlTestSuite: CacheMvccReplicatedBackupsTest.testBackupsCoherenceWithLargeOperations
- 0,0% fails in last 100 master runs.

{color:#d04437}SPI{color} [[tests 3|https://ci.ignite.apache.org/viewLog.html?buildId=2210212]]
* IgniteSpiTestSuite: TcpDiscoverySslSelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished
- 0,0% fails in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySslTrustedSelfTest.testNodeShutdownOnRingMessageWorkerStartNotFinished
- 0,0% fails in last 100 master runs.

{color:#d04437}MVCC Cache{color} [[tests 2|https://ci.ignite.apache.org/viewLog.html?buildId=2210229]]
* IgniteCacheMvccTestSuite: CacheMvccReplicatedCoordinatorFailoverTest.testAccountsTxScan_Server_Backups0_CoordinatorFails
- 0,0% fails in last 100 master runs.

{color:#d04437}Data Structures{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=2210260]]
* IgniteCacheDataStructuresSelfTestSuite: GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreConstantTopologyChangeNonFailoverSafe
- 0,0% fails in last 100 master runs.

{color:#d04437}PDS (Direct IO) 2{color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=2210265]]

{panel}
[TeamCity Run All Results|http://ci.ignite.apache.org/viewLog.html?buildId=2210285&amp;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)

Mime
View raw message