[jira] [Updated] (IGNITE-11349) MVCC: Deadlock in query pool when executing DML over caches with queryParallism > 1
[
https://issues.apache.org/jira/browse/IGNITE-11349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-11349:
---
Fix Version/s: (was: 2.9)
> MVCC: Deadlock in query pool when executing DML over caches with
> queryParallism > 1
> ---
>
> Key: IGNITE-11349
> URL: https://issues.apache.org/jira/browse/IGNITE-11349
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stability
>
> Reproducer: {{CacheMvccSelectForUpdateQueryBasicTest}}
> There is possible deadlock in {{QUERY_POOL}} when running massive SQL updates
> using queries without reducer when {{cache.queryParallelism > 1}}. These
> updates fire two step queries on each data node and both map and reduce
> phases are executed in the same {{QUERY_POOL}} which can lead to deadlock
> because reduce phase has blocking operation
> {{GridReduceQueryExecutor#awaitAllReplies}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11349) MVCC: Deadlock in query pool when executing DML over caches with queryParallism > 1
[
https://issues.apache.org/jira/browse/IGNITE-11349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-11349:
-
Fix Version/s: (was: 2.8)
2.9
> MVCC: Deadlock in query pool when executing DML over caches with
> queryParallism > 1
> ---
>
> Key: IGNITE-11349
> URL: https://issues.apache.org/jira/browse/IGNITE-11349
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stability
> Fix For: 2.9
>
>
> Reproducer: {{CacheMvccSelectForUpdateQueryBasicTest}}
> There is possible deadlock in {{QUERY_POOL}} when running massive SQL updates
> using queries without reducer when {{cache.queryParallelism > 1}}. These
> updates fire two step queries on each data node and both map and reduce
> phases are executed in the same {{QUERY_POOL}} which can lead to deadlock
> because reduce phase has blocking operation
> {{GridReduceQueryExecutor#awaitAllReplies}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-11349) MVCC: Deadlock in query pool when executing DML over caches with queryParallism > 1
[
https://issues.apache.org/jira/browse/IGNITE-11349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-11349:
-
Component/s: (was: mvcc)
> MVCC: Deadlock in query pool when executing DML over caches with
> queryParallism > 1
> ---
>
> Key: IGNITE-11349
> URL: https://issues.apache.org/jira/browse/IGNITE-11349
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stability
> Fix For: 2.8
>
>
> Reproducer: {{CacheMvccSelectForUpdateQueryBasicTest}}
> There is possible deadlock in {{QUERY_POOL}} when running massive SQL updates
> using queries without reducer when {{cache.queryParallelism > 1}}. These
> updates fire two step queries on each data node and both map and reduce
> phases are executed in the same {{QUERY_POOL}} which can lead to deadlock
> because reduce phase has blocking operation
> {{GridReduceQueryExecutor#awaitAllReplies}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11349) MVCC: Deadlock in query pool when executing DML over caches with queryParallism > 1
[
https://issues.apache.org/jira/browse/IGNITE-11349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-11349:
-
Component/s: mvcc
> MVCC: Deadlock in query pool when executing DML over caches with
> queryParallism > 1
> ---
>
> Key: IGNITE-11349
> URL: https://issues.apache.org/jira/browse/IGNITE-11349
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stability
> Fix For: 2.8
>
>
> Reproducer: {{CacheMvccSelectForUpdateQueryBasicTest}}
> There is possible deadlock in {{QUERY_POOL}} when running massive SQL updates
> using queries without reducer when {{cache.queryParallelism > 1}}. These
> updates fire two step queries on each data node and both map and reduce
> phases are executed in the same {{QUERY_POOL}} which can lead to deadlock
> because reduce phase has blocking operation
> {{GridReduceQueryExecutor#awaitAllReplies}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11349) MVCC: Deadlock in query pool when executing DML over caches with queryParallism > 1
[
https://issues.apache.org/jira/browse/IGNITE-11349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-11349:
-
Labels: mvcc_stability (was: )
> MVCC: Deadlock in query pool when executing DML over caches with
> queryParallism > 1
> ---
>
> Key: IGNITE-11349
> URL: https://issues.apache.org/jira/browse/IGNITE-11349
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Priority: Major
> Labels: mvcc_stability
> Fix For: 2.8
>
>
> Reproducer: {{CacheMvccSelectForUpdateQueryBasicTest}}
> There is possible deadlock in {{QUERY_POOL}} when running massive SQL updates
> using queries without reducer when {{cache.queryParallelism > 1}}. These
> updates fire two step queries on each data node and both map and reduce
> phases are executed in the same {{QUERY_POOL}} which can lead to deadlock
> because reduce phase has blocking operation
> {{GridReduceQueryExecutor#awaitAllReplies}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11349) MVCC: Deadlock in query pool when executing DML over caches with queryParallism > 1
[
https://issues.apache.org/jira/browse/IGNITE-11349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Kondakov updated IGNITE-11349:
Description:
Reproducer: {{CacheMvccSelectForUpdateQueryBasicTest}}
There is possible deadlock in {{QUERY_POOL}} when running massive SQL updates
using queries without reducer when {{cache.queryParallelism > 1}}. These
updates fire two step queries on each data node and both map and reduce phases
are executed in the same {{QUERY_POOL}} which can lead to deadlock because
reduce phase has blocking operation {{GridReduceQueryExecutor#awaitAllReplies}}.
> MVCC: Deadlock in query pool when executing DML over caches with
> queryParallism > 1
> ---
>
> Key: IGNITE-11349
> URL: https://issues.apache.org/jira/browse/IGNITE-11349
> Project: Ignite
> Issue Type: Bug
> Components: mvcc, sql
>Reporter: Roman Kondakov
>Priority: Major
> Fix For: 2.8
>
>
> Reproducer: {{CacheMvccSelectForUpdateQueryBasicTest}}
> There is possible deadlock in {{QUERY_POOL}} when running massive SQL updates
> using queries without reducer when {{cache.queryParallelism > 1}}. These
> updates fire two step queries on each data node and both map and reduce
> phases are executed in the same {{QUERY_POOL}} which can lead to deadlock
> because reduce phase has blocking operation
> {{GridReduceQueryExecutor#awaitAllReplies}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
