[jira] [Updated] (IGNITE-17911) Wal isn't enabled for some caches after cancelling of rebalance
[
https://issues.apache.org/jira/browse/IGNITE-17911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-17911:
-
Fix Version/s: 2.15
> Wal isn't enabled for some caches after cancelling of rebalance
> ---
>
> Key: IGNITE-17911
> URL: https://issues.apache.org/jira/browse/IGNITE-17911
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Fix For: 2.15
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> WAL can be disabled during a rebalance if a node does not own any partitions.
> When stopping a node, a shutdown hook is used, which calls
> {{IgniteionEx#stop}} with the {{cancel}} flag set to {{true}}. This wakes up
> the checkpoint thread and starts doing a checkpoint, which creates a
> checkpoint start marker. However, since the {{cancel}} flag was set to
> {{true}}, {{Checkpointer#writePages}} finishes immediately and the checkpoint
> end marker is not created.
> This means that we have not enabled WAL again, since the rebalance was
> interrupted, and we created a checkpoint start marker, but not the end
> marker. This leads to the node being started in maintenance mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17911) Wal isn't enabled for some caches after cancelling of rebalance
[
https://issues.apache.org/jira/browse/IGNITE-17911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-17911:
-
Fix Version/s: (was: 3.0.0-beta2)
> Wal isn't enabled for some caches after cancelling of rebalance
> ---
>
> Key: IGNITE-17911
> URL: https://issues.apache.org/jira/browse/IGNITE-17911
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> WAL can be disabled during a rebalance if a node does not own any partitions.
> When stopping a node, a shutdown hook is used, which calls
> {{IgniteionEx#stop}} with the {{cancel}} flag set to {{true}}. This wakes up
> the checkpoint thread and starts doing a checkpoint, which creates a
> checkpoint start marker. However, since the {{cancel}} flag was set to
> {{true}}, {{Checkpointer#writePages}} finishes immediately and the checkpoint
> end marker is not created.
> This means that we have not enabled WAL again, since the rebalance was
> interrupted, and we created a checkpoint start marker, but not the end
> marker. This leads to the node being started in maintenance mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17911) Wal isn't enabled for some caches after cancelling of rebalance
[
https://issues.apache.org/jira/browse/IGNITE-17911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-17911:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Wal isn't enabled for some caches after cancelling of rebalance
> ---
>
> Key: IGNITE-17911
> URL: https://issues.apache.org/jira/browse/IGNITE-17911
> Project: Ignite
> Issue Type: Task
>Reporter: Aleksandr Polovtcev
>Assignee: Aleksandr Polovtcev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> WAL can be disabled during a rebalance if a node does not own any partitions.
> When stopping a node, a shutdown hook is used, which calls
> {{IgniteionEx#stop}} with the {{cancel}} flag set to {{true}}. This wakes up
> the checkpoint thread and starts doing a checkpoint, which creates a
> checkpoint start marker. However, since the {{cancel}} flag was set to
> {{true}}, {{Checkpointer#writePages}} finishes immediately and the checkpoint
> end marker is not created.
> This means that we have not enabled WAL again, since the rebalance was
> interrupted, and we created a checkpoint start marker, but not the end
> marker. This leads to the node being started in maintenance mode.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
