You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/09/13 12:27:00 UTC
[jira] [Commented] (IGNITE-9411) Lock: make sure lock timeouts
works fine
[ https://issues.apache.org/jira/browse/IGNITE-9411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613412#comment-16613412 ]
ASF GitHub Bot commented on IGNITE-9411:
----------------------------------------
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/4745
IGNITE-9411: mvcc timeouts
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9411
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4745.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4745
----
commit db172dfc174614af7cbac8b5cecb2707b49e1bdc
Author: ipavlukhin <vo...@...>
Date: 2018-09-04T10:53:41Z
minors in CacheMvccSelectForUpdateQueryAbstractTest
commit c288988dd4f3622c8539ab7f6f3f84b5c08b7a0c
Author: ipavlukhin <vo...@...>
Date: 2018-09-04T11:13:01Z
use timeout modes in deadlock tests
commit e4bf4ae3bdcd8b049e66a90f30fb5720b34fd36c
Author: ipavlukhin <vo...@...>
Date: 2018-09-12T10:10:50Z
CacheMvccSqlLockTimeoutTest checking that waiting locks are timed out
commit 3ad0289ade9964e8a9ec74e10f3f05ed96d72bfc
Author: ipavlukhin <vo...@...>
Date: 2018-09-12T12:27:55Z
translate to timeout exception in reducer
commit 9d70e0ff36546ae05230481688b9a5f3b7bd7311
Author: ipavlukhin <vo...@...>
Date: 2018-09-12T12:29:53Z
translate to timeout exception in DmlStatementsProcessor
commit d34b1b88a498dd090efad058292f0ea19bbd5bef
Author: ipavlukhin <vo...@...>
Date: 2018-09-12T13:31:58Z
Merge branch 'master' into mvcc-lock-timeouts
commit 0bb7981f9459a797cde4aa97fa200b3502b6b923
Author: ipavlukhin <vo...@...>
Date: 2018-09-12T14:28:06Z
dirty conversion of remote timeout to TransactionTimeoutException, check new exception structure in test
commit 9539ef913a8bdd364d8a449c3b4e8aecaace57ef
Author: ipavlukhin <vo...@...>
Date: 2018-09-13T08:57:21Z
establish first design for timeout exceptions propagation, put missing timeouts in place
commit c7eea3664dec1aa09facee14ce24941dfa39b180
Author: ipavlukhin <vo...@...>
Date: 2018-09-13T09:59:34Z
remove extra stack trace garbage from test
commit 197f3e37c0cb2fa0337c880f2e66d55a878ce809
Author: ipavlukhin <vo...@...>
Date: 2018-09-13T10:31:22Z
use common method for timeout calculation in DmlStatementsProcessor
commit 980d43dcee8e8a540788c7305ad53280c88269c9
Author: ipavlukhin <vo...@...>
Date: 2018-09-13T12:06:58Z
fix forgotten tx variable initialization in IgniteH2Indexing
commit 75ba8821d844c8e7d250154b3fb68adaae842902
Author: ipavlukhin <vo...@...>
Date: 2018-09-13T12:15:51Z
remove duplicated tests from suite
----
> Lock: make sure lock timeouts works fine
> ----------------------------------------
>
> Key: IGNITE-9411
> URL: https://issues.apache.org/jira/browse/IGNITE-9411
> Project: Ignite
> Issue Type: Task
> Components: mvcc
> Reporter: Vladimir Ozerov
> Assignee: Ivan Pavlukhin
> Priority: Major
> Fix For: 2.7
>
>
> In SQL it is not uncommon that locks are taken in arbitrary order, what may lead to deadlocks. Fair deadlock detector is good solution in monolithic databases - just analyze dependency graph and kill one of conflicting transactions.
> We have a ticket to implement distributed deadlock detector in Ignite [1]. However, this solution is rather complex and may bring some overhead.
> For now it is better to rely on some timeout (global or per-transaction), and rollback TX when it fails to lock certain entry for a long time. Probably we already have this feature in some form. Need to add verify that it works and add more tests if needed.
> [1] https://issues.apache.org/jira/browse/IGNITE-9322
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)