[
https://issues.apache.org/jira/browse/IGNITE-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425609#comment-16425609
]
Alexei Scherbakov commented on IGNITE-6827:
-------------------------------------------
[~agura],
I don't agree what rollbackOnTopologyChangeTimeout is not a part of
transactional configuration.
This property is clearly part of transaction configuration, because it defines
when a rollback happens.
Moreover, ordinary user doesn't know what is "exchange" at all.
Nevertheless, it's clear for me what I have to add better description to this
parameter.
> 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)
