[ https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anton Vinogradov updated IGNITE-10663: -------------------------------------- Comment: was deleted (was: {panel:title=--> Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1} {color:#d04437}Thin client: Node.js{color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=3496581]] {panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3491169&buildTypeId=IgniteTests24Java8_RunAll]) > 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: 10h 10m > 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.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)