[
https://issues.apache.org/jira/browse/IGNITE-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246464#comment-16246464
]
Naresh Goty commented on IGNITE-6380:
-------------------------------------
Hi,
We applied the patch to v2.3, and we are seeing failures (below) when two nodes
are started at the same time and the node which started first has locks on
cache. Please refer to the use case here
(http://apache-ignite-users.70518.x6.nabble.com/Node-failed-to-startup-due-to-deadlock-td17839.html#a18080).
Snippet of error message:
ex=class o.a.i.compute.ComputeExecutionRejectedException: Pending topology
found - job execution within lock or transaction was canceled., hasRes=true,
isCancelled=false, isOccupied=true]
class org.apache.ignite.IgniteException: Remote job threw exception.
So, essentially when a new node is joining topology, any pending jobs were
stopped so that topology can succeed, but we intend to see the topology process
to wait till all the pending jobs are completed and locks were released instead
of stopping them.
Regards,
Naresh
> Exception should be thrown on cache creation attempt inside transaction
> -----------------------------------------------------------------------
>
> Key: IGNITE-6380
> URL: https://issues.apache.org/jira/browse/IGNITE-6380
> Project: Ignite
> Issue Type: Improvement
> Reporter: Yakov Zhdanov
> Assignee: Pavel Pereslegin
> Labels: newbie, usability
>
> Exception should be thrown on cache creation attempt inside transaction to
> prevent deadlocks since cache start triggers exchange and exchange cannot
> finish until all txs are finished.
> We need to check if thread owns a tx before starting cache and if it does
> then IllegalStateException should be thrown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
