[
https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-10663:
--------------------------------------
Description:
The main idea is to provide special "read from cache" mode which will read a
value from primary and all backups and will check that values are the same.
In case values differ they should be fixed according to the appropriate
strategy.
ToDo list:
1) {{cache.withConsistency().get(key)}} should guarantee values will be checked
across the topology and fixed if necessary.
2) LWW (Last Write Wins) strategy should be used for validation.
3) Since LWW and any other strategy do not guarantee that the correct value
will be chosen.
We have to record the event contains all values and the chosen one.
was:
The main idea is to provide special "read from cache" mode which will read a
value from primary and all backups and will check that values are the same.
In case values differ they should be fixed according to the appropriate
strategy.
{{cache.withConsistencyCheck().get(key)}} should guarantee values will be
checked across the topology and fixed if necessary.
LWW (Last Write Wins) strategy should be used for validation.
Since LWW and any other strategy do not guarantee that the correct value will
be chosen.
We have to record the event contains all values and the chosen one.
The event will allow to
- got we have an inconsistent state situation
- investigate which value is correct manually and refix if necessary
> Cache mode allows reads with consistency check and fix
> ------------------------------------------------------
>
> Key: IGNITE-10663
> URL: https://issues.apache.org/jira/browse/IGNITE-10663
> Project: Ignite
> Issue Type: Task
> Reporter: Anton Vinogradov
> Assignee: Anton Vinogradov
> Priority: Major
> Labels: iep-31
> Fix For: 2.8
>
>
> The main idea is to provide special "read from cache" mode which will read a
> value from primary and all backups and will check that values are the same.
> In case values differ they should be fixed according to the appropriate
> strategy.
> ToDo list:
> 1) {{cache.withConsistency().get(key)}} should guarantee values will be
> checked across the topology and fixed if necessary.
> 2) LWW (Last Write Wins) strategy should be used for validation.
> 3) Since LWW and any other strategy do not guarantee that the correct value
> will be chosen.
> We have to record the event contains all values and the chosen one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
