[
https://issues.apache.org/jira/browse/IGNITE-17875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17643871#comment-17643871
]
Anton Vinogradov commented on IGNITE-17875:
-------------------------------------------
> TX counters on PME (when all operations are finished) must contain no gaps.
Found that not all operations must be finished at PME (start) in case of crash.
Such operation will be fixed with TX recovery and subsequent counters
finalization, so, seems we should never have inconsistent counters not at PME
start, but at PME finish.
> 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)
