You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (JIRA)" <ji...@apache.org> on 2019/07/10 06:36:00 UTC
[jira] [Comment Edited] (IGNITE-10663) Implement cache mode allows
reads with consistency check and fix
[ https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881765#comment-16881765 ]
Anton Vinogradov edited comment on IGNITE-10663 at 7/10/19 6:35 AM:
--------------------------------------------------------------------
Merged to the master branch.
was (Author: avinogradov):
Merger to the master branch.
> Implement 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
>
> Time Spent: 18h
> Remaining Estimate: 0h
>
> 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.withReadRepair().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)