[
https://issues.apache.org/jira/browse/IGNITE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16665211#comment-16665211
]
Ignite TC Bot commented on IGNITE-9558:
---------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=2167237]]
* IgniteSpiTestSuite:
GridTcpCommunicationSpiRecoveryNoPairedConnectionsTest.testBlockRead2 - 0,0%
fails in last 100 master runs.
* IgniteSpiTestSuite: TcpDiscoverySslSelfTest.testMulticastIpFinder - 0,0%
fails in last 100 master runs.
{color:#d04437}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2167298]]
* exe: ServicesTest.TestWithKeepBinaryClient - 0,0% fails in last 100 master
runs.
{color:#d04437}Queries 2{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2167232]]
* IgniteBinaryCacheQueryTestSuite2:
IgniteCacheQueryStopOnCancelOrTimeoutDistributedJoinSelfTest.testTimeout2 -
0,0% fails in last 100 master runs.
{color:#d04437}Cache 7 (With Persistence){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2167279]]
* IgniteCacheTestSuite7:
TransactionIntegrityWithPrimaryIndexCorruptionTest.testPrimaryIndexCorruptionDuringCommitPrimaryNonColocatedThrowsChecked
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2167274]]
* IgniteCacheTestSuite2:
IgniteCacheClientNodeChangingTopologyTest.testPessimisticTx2 - 0,0% fails in
last 100 master runs.
{color:#d04437}Cache 6{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2167278]]
* IgniteCacheTestSuite6: CacheExchangeMergeTest.testMergeServerAndClientJoin1 -
0,0% fails in last 100 master runs.
{color:#d04437}JDBC Driver{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2167229]]
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2162502&buildTypeId=IgniteTests24Java8_RunAll]
> Avoid changing AffinityTopologyVersion on client connect when possible
> ----------------------------------------------------------------------
>
> Key: IGNITE-9558
> URL: https://issues.apache.org/jira/browse/IGNITE-9558
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: Alexey Goncharuk
> Assignee: Ilya Lantukh
> Priority: Major
> Fix For: 2.8
>
>
> Currently a client join event changes discovery topology version which, in
> turn, changes AffinityTopologyVersion.
> When a client maps transaction on new AffinityTopologyVersion, corresponding
> message is not processed on remote node until remote node receives the
> corresponding discovery event. If discovery event delivery is delayed for
> some reason, this will result in transaction stalls on client joins.
> Since the client node does not change partition affinity, we can safely map
> transactions on the previous topology version and do not change the affinity
> topology version at all.
> Some cases need special care and probably do not qualify for this
> optimization, such as when client has near cache or client hosts partition
> for REPLICATED cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
