You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2016/11/08 14:20:59 UTC
[jira] [Comment Edited] (IGNITE-4120) .NET: documentation and
example for deadlock-detection mechanism
[ https://issues.apache.org/jira/browse/IGNITE-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647681#comment-15647681 ]
Pavel Tupitsyn edited comment on IGNITE-4120 at 11/8/16 2:20 PM:
-----------------------------------------------------------------
Docs updated: https://apacheignite-net.readme.io/v1.7/docs/transactions#deadlock-detection-in-pessimistic-transactions
I can't include TransactionDeadlockException there because it is not released yet.
was (Author: ptupitsyn):
Docs updated: https://apacheignite-net.readme.io/v1.7/docs/transactions#deadlock-detection-in-pessimistic-transactions
> .NET: documentation and example for deadlock-detection mechanism
> ----------------------------------------------------------------
>
> Key: IGNITE-4120
> URL: https://issues.apache.org/jira/browse/IGNITE-4120
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
> Reporter: Denis Magda
> Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Presently the documentation and example about the deadlock detection mechanism are missing on .NET side. Let's fill this gap.
> - Documentation can be taken from Java side
> https://apacheignite.readme.io/v1.7/docs/transactions#deadlock-detection-in-pessimistic-transactions
> - The example scenario should be the following:
> -- start two threads inside of Ignite.NET process;
> -- each thread will start its own pessimistic transaction with timeout up to 10 seconds;
> -- the transactions must get to a deadlock;
> -- after the timeout expiration one of the transactions must succeed while the other must print out deadlock related information taking it from {{TransactionDeadlockException}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)