You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/03/11 06:33:04 UTC
[jira] [Updated] (IGNITE-10518) MVCC: Update operation may hangs on
backup on unstable topology.
[ https://issues.apache.org/jira/browse/IGNITE-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-10518:
-------------------------------------
Labels: Hanging failover (was: Hanging failover mvcc_stabilization_stage_1)
> MVCC: Update operation may hangs on backup on unstable topology.
> -----------------------------------------------------------------
>
> Key: IGNITE-10518
> URL: https://issues.apache.org/jira/browse/IGNITE-10518
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
> Priority: Critical
> Labels: Hanging, failover
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Update operation may hangs on backup awaiting next topology.
> Symptoms:
> # Exchange for topology version 6.1 has been finished.
> # Exchange for topology version 6.2 awaits for partition release.
> # DhtTxRemote waits for exchange.
> Seems, tx maps on outdated topology version.
> Reproducer IgniteTxCachePrimarySyncTest.testSingleKeyCommit() in Mvcc mode.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)