[
https://issues.apache.org/jira/browse/IGNITE-11793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-11793:
---------------------------------------
Description:
Currently with isolated updater (datastreamer + allowOverride=false) even for
transactional mode counters are generated independently on all owners.
In case of some nodes fail there is high risk of partition desync.
Also this mode couldn't be used together with concurrent transactions after
IGNITE-10078.
I suggest to introduce special loading mode for cache where concurrent updates
are prohibited until initial data loading (using isolated updater) is completed.
was:
Currently with isolated updater (datastream + allowOverride=false) even for
transactional mode counters are generated independently on all owners.
In case of some nodes fail there is high risk of partition desync.
Also this mode couldn't be used together with concurrent transactions after
IGNITE-10078.
I suggest to introduce special loading mode for cache where concurrent updates
are prohibited until initial data loading (using isolated updater) is completed.
> Improve isolated updater mode.
> ------------------------------
>
> Key: IGNITE-11793
> URL: https://issues.apache.org/jira/browse/IGNITE-11793
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexei Scherbakov
> Priority: Major
>
> Currently with isolated updater (datastreamer + allowOverride=false) even for
> transactional mode counters are generated independently on all owners.
> In case of some nodes fail there is high risk of partition desync.
> Also this mode couldn't be used together with concurrent transactions after
> IGNITE-10078.
> I suggest to introduce special loading mode for cache where concurrent
> updates are prohibited until initial data loading (using isolated updater) is
> completed.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
