You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (Jira)" <ji...@apache.org> on 2022/10/12 10:35:00 UTC
[jira] [Updated] (IGNITE-17880) Topology version must be extended with topology epoch
[ https://issues.apache.org/jira/browse/IGNITE-17880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anton Vinogradov updated IGNITE-17880:
--------------------------------------
Description:
Epoch must be incremented each time when topology version changed from 0 to 1 (when the cluster started or restarted).
Each epoch decrease or invariance on join must be logged as a warning.
Epoch must be logged at every topology version change.
This will
- help to determine how many times the cluster was restarted (and make it easier to determine when)
- checks that the part of the cluster which was restarted several times as a standalone cluster will never join the rest of the cluster with the lower epoch (check some segmentation and management problems)
was:
Epoch must be incremented each time when topology version changed from 0 to 1 (when the cluster started or restarted).
Each epoch decrease or invariance on join must be logged as a warning.
Epoch must be logged at every topology version change.
This will
- help to determine how many times the cluster was restarted (and make it easier to determine when)
- checks that the part of the cluster which was restarted sometimes as a standalone cluster will never join the rest of the cluster with the lower epoch (check some segmentation and management problems)
> Topology version must be extended with topology epoch
> -----------------------------------------------------
>
> Key: IGNITE-17880
> URL: https://issues.apache.org/jira/browse/IGNITE-17880
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Anton Vinogradov
> Priority: Major
>
> Epoch must be incremented each time when topology version changed from 0 to 1 (when the cluster started or restarted).
> Each epoch decrease or invariance on join must be logged as a warning.
> Epoch must be logged at every topology version change.
> This will
> - help to determine how many times the cluster was restarted (and make it easier to determine when)
> - checks that the part of the cluster which was restarted several times as a standalone cluster will never join the rest of the cluster with the lower epoch (check some segmentation and management problems)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)