You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Denis Garus (JIRA)" <ji...@apache.org> on 2018/05/16 14:32:00 UTC

[jira] [Commented] (IGNITE-7833) Find out possible ways to handle partition update counters inconsistency

    [ https://issues.apache.org/jira/browse/IGNITE-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477509#comment-16477509 ] 

Denis Garus commented on IGNITE-7833:
-------------------------------------

I'm resolving IGNITE-5979 and I'm sure that issue relates to this ticket.
1. I suggest to add to IGNITE-5979 link to this ticket like "depends on".
What do you think?
2. Can we fix this problem just marking partitions with invalid counter as LOST and restart MEP?

> Find out possible ways to handle partition update counters inconsistency
> ------------------------------------------------------------------------
>
>                 Key: IGNITE-7833
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7833
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Pavel Kovalenko
>            Assignee: Alexey Stelmak
>            Priority: Major
>
> We should think about possible ways to resolve the situation when we observe that partition update counters for the same partitions (primary-backup) are different on some nodes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)