ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Mashenkov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-11559) MVCC: Tx hangs on finish if StorageException occurs.
Date Mon, 18 Mar 2019 11:51:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-11559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Mashenkov updated IGNITE-11559:
--------------------------------------
    Labels: WAL mvcc_stability transactions  (was: hangs mvcc_stability transactions)

> MVCC: Tx hangs on finish if StorageException occurs.
> ----------------------------------------------------
>
>                 Key: IGNITE-11559
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11559
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc, persistence
>            Reporter: Andrew Mashenkov
>            Priority: Major
>              Labels: WAL, mvcc_stability, transactions
>
> By default non-mvcc transactions don't log their states in WAL log, so tx rollbacks without
hanging as there is nothing to save to WAL or PageMemory.
> So, it may be helpful to check case for non-mvcc tx with txState WAL-logging enabled
at first.
> When StorageException occurs during any mvcc tx operation enabled, then storage locks
become blocked. Then Ignite try to rollback Tx due to the error and try to save txState into
WAL and TxLog and hangs forever. A thread hangs awaiting uninterruptibly for next WAL segment
or lock released.
> Failure handler tries to stop a node and hangs as well.
> Looks like we shouldn't wait if kernal context become invalid.
> Good startpoint is IgniteWalFlush* tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message