You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Pavlukhin (JIRA)" <ji...@apache.org> on 2019/01/23 14:30:00 UTC

[jira] [Comment Edited] (IGNITE-10764) MVCC: Transactions failed to acquire lock within timeout

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

Ivan Pavlukhin edited comment on IGNITE-10764 at 1/23/19 2:29 PM:
------------------------------------------------------------------

Increasing timeout for a single transaction might fix mentioned test. Decreasing tx timeout allows to reproduce the issue easily. Exception message 
{noformat}Failed to acquire lock within provided timeout for transaction{noformat}
looks misleading.


was (Author: pavlukhin):
Increasing timeout for a single transaction might fix mentioned test. Decreasing tx timeout allows to reproduce the issue easily. Exception message 
{code}Failed to acquire lock within provided timeout for transaction{code}
looks misleading.

> MVCC: Transactions failed to acquire lock within timeout
> --------------------------------------------------------
>
>                 Key: IGNITE-10764
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10764
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc
>            Reporter: Roman Kondakov
>            Priority: Major
>              Labels: mvcc_stabilization_stage_1, transactions
>             Fix For: 2.8
>
>
> Some tests failed sporadically due to a transaction timeout though they update unique keys and deadlocks are not expected. It should be investigated.
> Reproducers:
> {{CacheMvccPartitionedSqlTxQueriesTest.testQueryInsertMultithread}}
> {{CacheMvccReplicatedSqlTxQueriesTest.testQueryInsertMultithread}}



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