[
https://issues.apache.org/jira/browse/IGNITE-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425740#comment-16425740
]
Andrey Gura edited comment on IGNITE-6827 at 4/4/18 3:46 PM:
-------------------------------------------------------------
This question is discussing on dev list. At least one more reviewer has the
same question. Please join to discussion on dev list.
Once again, transactions don't make any decisions on this timeout, only PME
takes this timeout into account. So it isn't transaction configuration.
was (Author: agura):
This question is discussing on dev list. At least one more reviewer has the
same question. Please join to discussion on dev list.
> Configurable rollback for long running transactions before partition exchange
> -----------------------------------------------------------------------------
>
> Key: IGNITE-6827
> URL: https://issues.apache.org/jira/browse/IGNITE-6827
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: Alexei Scherbakov
> Assignee: Alexei Scherbakov
> Priority: Major
> Fix For: 2.5
>
>
> Currently long running / buggy user transactions force partition exchange
> block on waiting for
> org.apache.ignite.internal.processors.cache.GridCacheSharedContext#partitionReleaseFuture,
> preventing all grid progress.
> I suggest introducing new global flag in TransactionConfiguration, like
> {{txRollbackTimeoutOnTopologyChange}}
> which will rollback exchange blocking transaction after the timeout.
> Still need to think what to do with other topology locking activities.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
