You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Shishkov (Jira)" <ji...@apache.org> on 2023/04/10 09:58:00 UTC
[jira] [Assigned] (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 ]
Ilya Shishkov reassigned IGNITE-17880:
--------------------------------------
Assignee: (was: Ilya Shishkov)
> 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
> Labels: ise
>
> Epoch must be presented as a timestamp and version pair.
> Epoch timestamp must represent epoch start time.
> Epoch major version must be incremented each time when topology version changed from 0 to 1 (when the cluster started or restarted).
> Epoch minor version should be changed on every baseline change.
> Node's epoch version must be increased or keeped as is on node join.
> Each decreasing must be logged as an error.
> Epoch (version and timestamp) 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/segmented 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)