You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladislav Pyatkov (Jira)" <ji...@apache.org> on 2026/04/27 13:16:00 UTC
[jira] [Updated] (IGNITE-28612) Entry visibility violation in transactional replication cache with one backup and near
[ https://issues.apache.org/jira/browse/IGNITE-28612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladislav Pyatkov updated IGNITE-28612:
---------------------------------------
Description:
h3. Motivation
It is not a big issue, but nevertheless, a sequential guarantee is not to be violated even in case the updates come through the different nodes.
I believe this is an issue in a near cache, because if I wait several extra milliseconds before checking the cache, it passes.
h3. Definition of done
The attached test ought to pass.
was:
h3. Motivation
It is not a big issue, but nevertheless, a sequential guarantee is not to be violated even in case the updates come through the different nodes.
h3. Definition of done
The attached test ought to pass.
> Entry visibility violation in transactional replication cache with one backup and near
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-28612
> URL: https://issues.apache.org/jira/browse/IGNITE-28612
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-2
> Attachments: CacheWthNearEntryVisibilityTest.java
>
>
> h3. Motivation
> It is not a big issue, but nevertheless, a sequential guarantee is not to be violated even in case the updates come through the different nodes.
> I believe this is an issue in a near cache, because if I wait several extra milliseconds before checking the cache, it passes.
> h3. Definition of done
> The attached test ought to pass.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)