[ https://issues.apache.org/jira/browse/IGNITE-9310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-9310.
-------------------------------------
Resolution: Won't Fix
This is no longer needed, as we do not create caches any more.
> SQL: throw exception when missing cache is attempted to be created inside a transaction
> ---------------------------------------------------------------------------------------
>
> Key: IGNITE-9310
> URL: https://issues.apache.org/jira/browse/IGNITE-9310
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 2.6
> Reporter: Vladimir Ozerov
> Assignee: Igor Seliverstov
> Priority: Minor
> Attachments: CacheCreationItTransactionSelfTest.java
>
>
> See \{{org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing#prepareStatementAndCaches}}.
This method might be called inside a transaction (both MVCC and non-MVCC modes). If we do
not have any protective mechanics (need to check), then this call may lead to cache creation
on a client, which in turn will wait for all TXes to finish, including current one, leading
to a deadlock.
> # Create tests confirming the problem
> # If hang is reproduced - add a check for ongoing transaction and throw an exception
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
|