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

Anton Vinogradov updated IGNITE-18332:
--------------------------------------
    Description: 
{{GridDhtPartitionsExchangeFuture#finalizePartitionCounters}} is used to close 
the gaps at partition counters after the craches (automatically).
Even at the PME-free switch (when backup must become primary asap) it is not 
correct to loose the counters data (gaps).

At PME-free switch, due to tx recovery, it's expected to have same gaps on 
backups, but primary may have some gaps committed.
Closing the gaps also maks backups's operations as committed. 
And we'll gain inconsistent state ot ex-primary join ?(since rebalance will see 
no gaps on backups).

Gaps must be closed only ecxplicitly using the consistency repair utility.



  was:
{{GridDhtPartitionsExchangeFuture#finalizePartitionCounters}} is used to hide 
gaps at partition counters after the craches.
Even at the PME-free switch (when backup must become primary asap) it is not 
correct to loose the counters data (gaps).

Main problem here is that "different gaps" means "different content" and 
calling {{finalizePartitionCounters()}} we mark different content as the same.




> Get rid of implicit partition counters finalization
> ---------------------------------------------------
>
>                 Key: IGNITE-18332
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18332
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Anton Vinogradov
>            Priority: Major
>              Labels: ise
>
> {{GridDhtPartitionsExchangeFuture#finalizePartitionCounters}} is used to 
> close the gaps at partition counters after the craches (automatically).
> Even at the PME-free switch (when backup must become primary asap) it is not 
> correct to loose the counters data (gaps).
> At PME-free switch, due to tx recovery, it's expected to have same gaps on 
> backups, but primary may have some gaps committed.
> Closing the gaps also maks backups's operations as committed. 
> And we'll gain inconsistent state ot ex-primary join ?(since rebalance will 
> see no gaps on backups).
> Gaps must be closed only ecxplicitly using the consistency repair utility.



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

Reply via email to