ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Gura (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4937) Transactions deadlock detection should happen on each grid hang
Date Mon, 10 Apr 2017 13:21:41 GMT

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

Andrey Gura commented on IGNITE-4937:
-------------------------------------

>From my point of view it is helpful improvement but we should be careful here because
we can block local operation by starting distributed operation.

Also I think we should add deadlock detection triggers that can be activated periodically
(configuration setting) or manually (e.g. via MBean).

> Transactions deadlock detection should happen on each grid hang
> ---------------------------------------------------------------
>
>                 Key: IGNITE-4937
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4937
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Anton Vinogradov
>            Priority: Critical
>
> Each "Failed to wait for partition map exchange" or similar should cause such check.

> Check can be added to org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager#dumpPendingObjects
> or/and
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager#dumpLongRunningOperations



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message