You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maksim Timonin (Jira)" <ji...@apache.org> on 2022/11/22 08:33:00 UTC
[jira] [Assigned] (IGNITE-17875) TX counters with gaps must be logged on every PME
[ https://issues.apache.org/jira/browse/IGNITE-17875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maksim Timonin reassigned IGNITE-17875:
---------------------------------------
Assignee: Maksim Timonin
> TX counters with gaps must be logged on every PME
> -------------------------------------------------
>
> Key: IGNITE-17875
> URL: https://issues.apache.org/jira/browse/IGNITE-17875
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Anton Vinogradov
> Assignee: Maksim Timonin
> Priority: Major
> Labels: ise
>
> TX counters on PME (when all operations are finished) must contain no gaps.
> Such partitions should be listed (with counters) with a special warning.
> Currently, we already have a "Failed to update the counter ..." warning which is logged when the primary tries to set the backup's update counter to its LWM which is less than the backup's HWM.
> But, the better case is to list all broken partitions during the full message calculation during the PME at the coordinator.
> All counters must be listed for every partition which has at least one counter with gaps.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)