[ 
https://issues.apache.org/jira/browse/IGNITE-17875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov updated IGNITE-17875:
--------------------------------------
    Description: 
TX counters on PME (when all operations are finished) must contain no gaps.
Such partitions should be listed (with counters) with a special warning.
This warning will help to determine that consistency recovery is required.

Currently, we already have a warning "Failed to update the counter ..." which 
cause when primary tries to set backup's update counter to it's LWM which is 
less than backups's HWM. 
But there will be no warning when primary and backups has the same LWM and some 
gaps.

  was:
TX counters on PME (when all operations are finished) must contain no gaps.
Such partitions should be listed (with counters) with a special warning.
This warning will help to fix the bugs that causes this.


> 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
>            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.
> This warning will help to determine that consistency recovery is required.
> Currently, we already have a warning "Failed to update the counter ..." which 
> cause when primary tries to set backup's update counter to it's LWM which is 
> less than backups's HWM. 
> But there will be no warning when primary and backups has the same LWM and 
> some gaps.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to