[jira] [Updated] (IGNITE-9310) SQL: throw exception when missing cache is attempted to be created inside a transaction
[
https://issues.apache.org/jira/browse/IGNITE-9310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9310:
Ignite Flags: (was: Docs Required)
> 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)
[jira] [Updated] (IGNITE-9310) SQL: throw exception when missing cache is attempted to be created inside a transaction
[
https://issues.apache.org/jira/browse/IGNITE-9310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9310:
Fix Version/s: (was: 2.7)
> 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)
[jira] [Updated] (IGNITE-9310) SQL: throw exception when missing cache is attempted to be created inside a transaction
[
https://issues.apache.org/jira/browse/IGNITE-9310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Seliverstov updated IGNITE-9310:
-
Priority: Minor (was: Critical)
> 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
> Fix For: 2.7
>
> 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)
[jira] [Updated] (IGNITE-9310) SQL: throw exception when missing cache is attempted to be created inside a transaction
[
https://issues.apache.org/jira/browse/IGNITE-9310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Seliverstov updated IGNITE-9310:
-
Attachment: CacheCreationItTransactionSelfTest.java
> 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: Critical
> Fix For: 2.7
>
> 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)
[jira] [Updated] (IGNITE-9310) SQL: throw exception when missing cache is attempted to be created inside a transaction
[
https://issues.apache.org/jira/browse/IGNITE-9310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Seliverstov updated IGNITE-9310:
-
Component/s: (was: mvcc)
> 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: Critical
> Fix For: 2.7
>
>
> 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)
