[
https://issues.apache.org/jira/browse/IGNITE-25642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-25642:
---------------------------------------
Description: ADDING and LEAVING events might be reordered. If subsequent
ADDED is reordered with preceding LEAVING, we get 2 ADDED in a row. Second
ADDED should replace previous version of the node (having same consistentId and
address, but different ID). Instead it currently just adds another node version
alongside with the old one. This causes DuplicateConsistentIdExceptions thrown
when getting a node by consistentId. (was: ADDING and LEAVING events might be
reordered. If subsequent ADDED is reordered with preceding LEAVING, we get 2
ADDED in a row. Second ADDED should replace previous version of the node
(having same consistentId and address, but different ID). Instead it currently
just adds another node version alongside with the old one. This causes)
> DuplicateConsistentIdException due to ADDED events reordering
> -------------------------------------------------------------
>
> Key: IGNITE-25642
> URL: https://issues.apache.org/jira/browse/IGNITE-25642
> Project: Ignite
> Issue Type: Bug
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ADDING and LEAVING events might be reordered. If subsequent ADDED is
> reordered with preceding LEAVING, we get 2 ADDED in a row. Second ADDED
> should replace previous version of the node (having same consistentId and
> address, but different ID). Instead it currently just adds another node
> version alongside with the old one. This causes
> DuplicateConsistentIdExceptions thrown when getting a node by consistentId.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
