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-9944) MVCC TX: GridDhtTxAbstractEnlistFuture near nodes update race.
Date Mon, 22 Oct 2018 15:22:00 GMT

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

Ignite TC Bot commented on IGNITE-9944:

{panel:title=Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Java Client{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=2139214]]
* IgniteClientTestSuite: TcpRouterMultiNodeSelfTest.testTopologyListener - 0,0% fails in last
100 master runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 2|https://ci.ignite.apache.org/viewLog.html?buildId=2139289]]
* dll: IgniteConfigurationTest.TestMulticastIpFinder - 2,0% fails in last 100 master runs.

[TeamCity Run All|http://ci.ignite.apache.org/viewLog.html?buildId=2139297&amp;buildTypeId=IgniteTests24Java8_RunAll]

> MVCC TX: GridDhtTxAbstractEnlistFuture near nodes update race.
> --------------------------------------------------------------
>                 Key: IGNITE-9944
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9944
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc
>            Reporter: Roman Kondakov
>            Assignee: Ivan Pavlukhin
>            Priority: Major
>             Fix For: 2.7
> When {{GridDhtTxAbstractEnlistFuture#skipNearNodeUpdates}} is set to true it can cause
failure on backup node during rebalancing. Possible scenario:
> # First entry is enlisted before rabalance was started and therefore it's backup node
is added to {{GridDhtTxLocalAdapter#addLockTransactionNode}} in {{GridDhtTxAbstractEnlistFuture#addToBatch}}
method. Note: in this case remote tx is not started on remote note.
> # Next entry could be processed when rebalance is already started and therefore this
optimization will be skipped. In this case updated entry will be sent to backup node as usual
in DhtEnlistRequest. 
> # But instead of sending {{GridDhtTxQueryFirstEnlistRequest}}, the {{GridDhtTxQueryEnlistRequest}}
will be sent because near node has already been added to tx lock nodes list.
> # When this request arrives in {{GridDhtTransactionalCacheAdapter#processDhtTxQueryEnlistRequest}},
the "Can not find a transaction" exception will be thrown.
> Possible solution: we need to send {{GridDhtTxQueryFirstEnlistRequest}} in these cases.

This message was sent by Atlassian JIRA

View raw message