[jira] [Commented] (IGNITE-13818) Add extended logging topology for node start
[
https://issues.apache.org/jira/browse/IGNITE-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318724#comment-17318724
]
Ignite TC Bot commented on IGNITE-13818:
{panel:title=Branch: [pull/8559/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8559/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5957197&buildTypeId=IgniteTests24Java8_RunAll]
> Add extended logging topology for node start
>
>
> Key: IGNITE-13818
> URL: https://issues.apache.org/jira/browse/IGNITE-13818
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maria Makedonskaya
>Assignee: Maria Makedonskaya
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> At start of the node write topology - the number of server and client nodes,
> I would like to expand the list of nodes (information about each node: order,
> id, host, ip), this will help in the case when the logs are only from one
> node, and when there are logs from all nodes it will speed up the search for
> coordinator or find the problem node id which was in the transaction
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13818) Add extended logging topology for node left/join a grid
[ https://issues.apache.org/jira/browse/IGNITE-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Makedonskaya updated IGNITE-13818: Summary: Add extended logging topology for node left/join a grid (was: Add extended logging topology for node start) > Add extended logging topology for node left/join a grid > --- > > Key: IGNITE-13818 > URL: https://issues.apache.org/jira/browse/IGNITE-13818 > Project: Ignite > Issue Type: Improvement >Reporter: Maria Makedonskaya >Assignee: Maria Makedonskaya >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > At start of the node write topology - the number of server and client nodes, > I would like to expand the list of nodes (information about each node: order, > id, host, ip), this will help in the case when the logs are only from one > node, and when there are logs from all nodes it will speed up the search for > coordinator or find the problem node id which was in the transaction -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13818) Add extended logging topology for node left/join a grid
[ https://issues.apache.org/jira/browse/IGNITE-13818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318748#comment-17318748 ] Maria Makedonskaya commented on IGNITE-13818: - [~slava.koptilin], I fixed your comment. Could you pls take a look again? > Add extended logging topology for node left/join a grid > --- > > Key: IGNITE-13818 > URL: https://issues.apache.org/jira/browse/IGNITE-13818 > Project: Ignite > Issue Type: Improvement >Reporter: Maria Makedonskaya >Assignee: Maria Makedonskaya >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > At start of the node write topology - the number of server and client nodes, > I would like to expand the list of nodes (information about each node: order, > id, host, ip), this will help in the case when the logs are only from one > node, and when there are logs from all nodes it will speed up the search for > coordinator or find the problem node id which was in the transaction -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14497) Move background task deletion at the end of next checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318808#comment-17318808 ] Denis Chudov commented on IGNITE-14497: --- [~makedonskaya] lgtm > Move background task deletion at the end of next checkpoint > --- > > Key: IGNITE-14497 > URL: https://issues.apache.org/jira/browse/IGNITE-14497 > Project: Ignite > Issue Type: Bug >Reporter: Maria Makedonskaya >Assignee: Maria Makedonskaya >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In [1] has been described scenario of the race that makes possible a > situation when information from metastore has been deleted and part of the > index is still present in the storage. > Actually, fix in [1] that has been done in slightly different way, however, > it strongly decreases possibility of the race. Removal of the background task > has been moved to beginning of the next checkpoint. It was done this way, > because the problem was in case when node unexpectedly failed in the middle > of next checkpoint and after restart task failed on check of deleted index > metaPage. The check was done in [2]. > In current issue, we only move background task deletion at the end of the > next checkpoint. > [1][IGNITE-13382|https://issues.apache.org/jira/browse/IGNITE-13382] > [2][IGNITE-14447|https://issues.apache.org/jira/browse/IGNITE-14447] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14497) Move background task deletion at the end of next checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Makedonskaya updated IGNITE-14497: Reviewer: Ivan Bessonov (was: Denis Chudov) > Move background task deletion at the end of next checkpoint > --- > > Key: IGNITE-14497 > URL: https://issues.apache.org/jira/browse/IGNITE-14497 > Project: Ignite > Issue Type: Bug >Reporter: Maria Makedonskaya >Assignee: Maria Makedonskaya >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In [1] has been described scenario of the race that makes possible a > situation when information from metastore has been deleted and part of the > index is still present in the storage. > Actually, fix in [1] that has been done in slightly different way, however, > it strongly decreases possibility of the race. Removal of the background task > has been moved to beginning of the next checkpoint. It was done this way, > because the problem was in case when node unexpectedly failed in the middle > of next checkpoint and after restart task failed on check of deleted index > metaPage. The check was done in [2]. > In current issue, we only move background task deletion at the end of the > next checkpoint. > [1][IGNITE-13382|https://issues.apache.org/jira/browse/IGNITE-13382] > [2][IGNITE-14447|https://issues.apache.org/jira/browse/IGNITE-14447] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14497) Move background task deletion at the end of next checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318810#comment-17318810 ] Maria Makedonskaya commented on IGNITE-14497: - [~ibessonov], could you pls take a look? > Move background task deletion at the end of next checkpoint > --- > > Key: IGNITE-14497 > URL: https://issues.apache.org/jira/browse/IGNITE-14497 > Project: Ignite > Issue Type: Bug >Reporter: Maria Makedonskaya >Assignee: Maria Makedonskaya >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In [1] has been described scenario of the race that makes possible a > situation when information from metastore has been deleted and part of the > index is still present in the storage. > Actually, fix in [1] that has been done in slightly different way, however, > it strongly decreases possibility of the race. Removal of the background task > has been moved to beginning of the next checkpoint. It was done this way, > because the problem was in case when node unexpectedly failed in the middle > of next checkpoint and after restart task failed on check of deleted index > metaPage. The check was done in [2]. > In current issue, we only move background task deletion at the end of the > next checkpoint. > [1][IGNITE-13382|https://issues.apache.org/jira/browse/IGNITE-13382] > [2][IGNITE-14447|https://issues.apache.org/jira/browse/IGNITE-14447] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13444) Cluster deactivation could lead to JVM crash.
[
https://issues.apache.org/jira/browse/IGNITE-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Makedonskaya updated IGNITE-13444:
Summary: Cluster deactivation could lead to JVM crash. (was: Cluster
deactivation and stop could lead to JVM crash.)
> Cluster deactivation could lead to JVM crash.
> -
>
> Key: IGNITE-13444
> URL: https://issues.apache.org/jira/browse/IGNITE-13444
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maria Makedonskaya
>Assignee: Maria Makedonskaya
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We could get JVM crash if a cluster has indexes and the node has been stopped
> right after deactivation.We could get JVM crash if a cluster has indexes and
> the node has been stopped right after deactivation.
> Scenario:
> * Apply patch:
> {code:java}
> Index:
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.javaIDEA
> additional info:Subsystem:
> com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
>
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
> (revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
> (date 1587246501828)@@ -30,6 +30,7 @@ import
> org.apache.ignite.internal.processors.query.h2.database.H2Tree; import
> org.apache.ignite.internal.util.typedef.internal.CU; import
> org.apache.ignite.internal.util.typedef.internal.S;+import
> org.apache.ignite.internal.util.typedef.internal.U; import static
> org.apache.ignite.internal.metric.IoStatisticsType.SORTED_INDEX; @@ -155,6
> +156,8 @@ BPlusTree tree = trees0.get(i);
> try \{+ U.sleep(1L);+
> tree.destroy(null, true); } catch
> (IgniteCheckedException e) \{Index:
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.javaIDEA
> additional info:Subsystem:
> com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
>
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
> (revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
> (date 1587247548691)@@ -30,6 +30,7 @@ import
> org.apache.ignite.failure.StopNodeFailureHandler; import
> org.apache.ignite.internal.IgniteEx; import
> org.apache.ignite.internal.processors.cache.index.AbstractIndexingCommonTest;+import
> org.apache.ignite.internal.util.typedef.internal.U; import
> org.apache.ignite.testframework.GridTestUtils; import
> org.h2.result.LazyResult; import org.h2.result.ResultInterface;@@ -78,6 +79,8
> @@ @Override protected void afterTest() throws Exception {
> stopAllGrids(); + U.sleep(2L);+ super.afterTest(); }
> {code}
> * Start {{LocalQueryLazyTest#testDeactivateWithOpenCursor()}} test without
> {{-ea}} VM option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13444) Cluster deactivation could lead to JVM crash.
[
https://issues.apache.org/jira/browse/IGNITE-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maria Makedonskaya updated IGNITE-13444:
Description:
We could get JVM crash if a cluster has indexes and index deletion task tries
to run on deactivated grid. We shouldn't start new tasks on a deactivated
grid. Also, interrupt the execution of current tasks.
Scenario:
* Apply patch:
{code:java}
Index:
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.javaIDEA
additional info:Subsystem:
com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
(revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
(date 1587246501828)@@ -30,6 +30,7 @@ import
org.apache.ignite.internal.processors.query.h2.database.H2Tree; import
org.apache.ignite.internal.util.typedef.internal.CU; import
org.apache.ignite.internal.util.typedef.internal.S;+import
org.apache.ignite.internal.util.typedef.internal.U; import static
org.apache.ignite.internal.metric.IoStatisticsType.SORTED_INDEX; @@ -155,6
+156,8 @@ BPlusTree tree = trees0.get(i); try
\{+ U.sleep(1L);+ tree.destroy(null,
true); } catch (IgniteCheckedException e)
\{Index:
modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.javaIDEA
additional info:Subsystem:
com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
(revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
(date 1587247548691)@@ -30,6 +30,7 @@ import
org.apache.ignite.failure.StopNodeFailureHandler; import
org.apache.ignite.internal.IgniteEx; import
org.apache.ignite.internal.processors.cache.index.AbstractIndexingCommonTest;+import
org.apache.ignite.internal.util.typedef.internal.U; import
org.apache.ignite.testframework.GridTestUtils; import org.h2.result.LazyResult;
import org.h2.result.ResultInterface;@@ -78,6 +79,8 @@ @Override protected
void afterTest() throws Exception { stopAllGrids(); +
U.sleep(2L);+ super.afterTest(); }
{code}
* Start {{LocalQueryLazyTest#testDeactivateWithOpenCursor()}} test without
{{-ea}} VM option.
was:
We could get JVM crash if a cluster has indexes and the node has been stopped
right after deactivation.We could get JVM crash if a cluster has indexes and
the node has been stopped right after deactivation.
Scenario:
* Apply patch:
{code:java}
Index:
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.javaIDEA
additional info:Subsystem:
com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
(revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
(date 1587246501828)@@ -30,6 +30,7 @@ import
org.apache.ignite.internal.processors.query.h2.database.H2Tree; import
org.apache.ignite.internal.util.typedef.internal.CU; import
org.apache.ignite.internal.util.typedef.internal.S;+import
org.apache.ignite.internal.util.typedef.internal.U; import static
org.apache.ignite.internal.metric.IoStatisticsType.SORTED_INDEX; @@ -155,6
+156,8 @@ BPlusTree tree = trees0.get(i); try
\{+ U.sleep(1L);+ tree.destroy(null,
true); } catch (IgniteCheckedException e)
\{Index:
modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.javaIDEA
additional info:Subsystem:
com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
(revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
(date 1587247548691)@@ -30,6 +30,7 @@ import
org.apache.ignite.failure.StopNodeFailureHandler; import
org.apache
[jira] [Commented] (IGNITE-14321) Forced index rebuilding does not work correctly
[
https://issues.apache.org/jira/browse/IGNITE-14321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319026#comment-17319026
]
Ignite TC Bot commented on IGNITE-14321:
{panel:title=Branch: [pull/8962/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8962/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5955588]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
ForceRebuildIndexTest.testForceRebuildIndexesAfterExchange - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
ForceRebuildIndexTest.testSequentialForceRebuildIndexes - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
ForceRebuildIndexTest.testSequentialRebuildIndexesOnExchange - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5955621&buildTypeId=IgniteTests24Java8_RunAll]
> Forced index rebuilding does not work correctly
> ---
>
> Key: IGNITE-14321
> URL: https://issues.apache.org/jira/browse/IGNITE-14321
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> At the moment, it is not possible to force an index rebuild twice (or more)
> even if the first run fails, and this also applies to command *control.sh
> --cache indexes_force_rebuild*.
> Thus, we need to fix:
> * *GridCacheDatabaseSharedManager#forceRebuildIndexes*
> * *CacheIndexesForceRebuild#execute*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13444) Cluster deactivation could lead to JVM crash.
[
https://issues.apache.org/jira/browse/IGNITE-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319036#comment-17319036
]
Ignite TC Bot commented on IGNITE-13444:
{panel:title=Branch: [pull/8244/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8244/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}PDS (Indexing){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5962675]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
LongDestroyDurableBackgroundTaskTest.testClusterDeactivationShouldPassWithoutErrors
- PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5962324&buildTypeId=IgniteTests24Java8_RunAll]
> Cluster deactivation could lead to JVM crash.
> -
>
> Key: IGNITE-13444
> URL: https://issues.apache.org/jira/browse/IGNITE-13444
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Maria Makedonskaya
>Assignee: Maria Makedonskaya
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We could get JVM crash if a cluster has indexes and index deletion task tries
> to run on deactivated grid. We shouldn't start new tasks on a deactivated
> grid. Also, interrupt the execution of current tasks.
> Scenario:
> * Apply patch:
> {code:java}
> Index:
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.javaIDEA
> additional info:Subsystem:
> com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
>
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
> (revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
> modules/indexing/src/main/java/org/apache/ignite/internal/processors/query/h2/DurableBackgroundCleanupIndexTreeTask.java
> (date 1587246501828)@@ -30,6 +30,7 @@ import
> org.apache.ignite.internal.processors.query.h2.database.H2Tree; import
> org.apache.ignite.internal.util.typedef.internal.CU; import
> org.apache.ignite.internal.util.typedef.internal.S;+import
> org.apache.ignite.internal.util.typedef.internal.U; import static
> org.apache.ignite.internal.metric.IoStatisticsType.SORTED_INDEX; @@ -155,6
> +156,8 @@ BPlusTree tree = trees0.get(i);
> try \{+ U.sleep(1L);+
> tree.destroy(null, true); } catch
> (IgniteCheckedException e) \{Index:
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.javaIDEA
> additional info:Subsystem:
> com.intellij.openapi.diff.impl.patch.CharsetEP<+>UTF-8===---
>
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
> (revision fc4ed408be9a0bb8d1f3d2c538a1b2ce8951320e)+++
> modules/indexing/src/test/java/org/apache/ignite/internal/processors/query/LocalQueryLazyTest.java
> (date 1587247548691)@@ -30,6 +30,7 @@ import
> org.apache.ignite.failure.StopNodeFailureHandler; import
> org.apache.ignite.internal.IgniteEx; import
> org.apache.ignite.internal.processors.cache.index.AbstractIndexingCommonTest;+import
> org.apache.ignite.internal.util.typedef.internal.U; import
> org.apache.ignite.testframework.GridTestUtils; import
> org.h2.result.LazyResult; import org.h2.result.ResultInterface;@@ -78,6 +79,8
> @@ @Override protected void afterTest() throws Exception {
> stopAllGrids(); + U.sleep(2L);+ super.afterTest(); }
> {code}
> * Start {{LocalQueryLazyTest#testDeactivateWithOpenCursor()}} test without
> {{-ea}} VM option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13976) WAL disable/enable with node restarts results in mismatching state, data loss
[ https://issues.apache.org/jira/browse/IGNITE-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-13976: - Fix Version/s: 2.11 > WAL disable/enable with node restarts results in mismatching state, data loss > - > > Key: IGNITE-13976 > URL: https://issues.apache.org/jira/browse/IGNITE-13976 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.9.1 >Reporter: Ilya Kasnacheev >Assignee: Sergey Chugunov >Priority: Critical > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > If you try to enable/disable WAL on unstable topology, you will get to state > when WAL status is undefined, nodes might have different wall status and the > only way to fix it is to restart the cluster, which will lead to data loss > because ignite removes data if WAL is disabled on restart. > See the reproducer in PR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14497) Move background task deletion at the end of next checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318810#comment-17318810 ] Maria Makedonskaya edited comment on IGNITE-14497 at 4/12/21, 6:54 AM: --- [~sergey-chugunov] , could you pls take a look? was (Author: makedonskaya): [~ibessonov], could you pls take a look? > Move background task deletion at the end of next checkpoint > --- > > Key: IGNITE-14497 > URL: https://issues.apache.org/jira/browse/IGNITE-14497 > Project: Ignite > Issue Type: Bug >Reporter: Maria Makedonskaya >Assignee: Maria Makedonskaya >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In [1] has been described scenario of the race that makes possible a > situation when information from metastore has been deleted and part of the > index is still present in the storage. > Actually, fix in [1] that has been done in slightly different way, however, > it strongly decreases possibility of the race. Removal of the background task > has been moved to beginning of the next checkpoint. It was done this way, > because the problem was in case when node unexpectedly failed in the middle > of next checkpoint and after restart task failed on check of deleted index > metaPage. The check was done in [2]. > In current issue, we only move background task deletion at the end of the > next checkpoint. > [1][IGNITE-13382|https://issues.apache.org/jira/browse/IGNITE-13382] > [2][IGNITE-14447|https://issues.apache.org/jira/browse/IGNITE-14447] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14497) Move background task deletion at the end of next checkpoint
[ https://issues.apache.org/jira/browse/IGNITE-14497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Makedonskaya updated IGNITE-14497: Reviewer: Sergey Chugunov (was: Ivan Bessonov) > Move background task deletion at the end of next checkpoint > --- > > Key: IGNITE-14497 > URL: https://issues.apache.org/jira/browse/IGNITE-14497 > Project: Ignite > Issue Type: Bug >Reporter: Maria Makedonskaya >Assignee: Maria Makedonskaya >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In [1] has been described scenario of the race that makes possible a > situation when information from metastore has been deleted and part of the > index is still present in the storage. > Actually, fix in [1] that has been done in slightly different way, however, > it strongly decreases possibility of the race. Removal of the background task > has been moved to beginning of the next checkpoint. It was done this way, > because the problem was in case when node unexpectedly failed in the middle > of next checkpoint and after restart task failed on check of deleted index > metaPage. The check was done in [2]. > In current issue, we only move background task deletion at the end of the > next checkpoint. > [1][IGNITE-13382|https://issues.apache.org/jira/browse/IGNITE-13382] > [2][IGNITE-14447|https://issues.apache.org/jira/browse/IGNITE-14447] -- This message was sent by Atlassian Jira (v8.3.4#803005)
