ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix
Date Wed, 13 Mar 2019 19:53:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-10663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792058#comment-16792058

Ignite TC Bot commented on IGNITE-10663:

{panel:title=--&gt; Run :: All: Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests 9|https://ci.ignite.apache.org/viewLog.html?buildId=3306852]]
* exe: CacheParityTest.TestCache - 0,0% fails in last 364 master runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 5|https://ci.ignite.apache.org/viewLog.html?buildId=3306855]]
* dll: CacheParityTest.TestCache - 0,0% fails in last 373 master runs.

{color:#d04437}Data Structures{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=3306861]]
* IgniteCacheDataStructuresSelfTestSuite: ExplicitTransactionalCacheConsistencyTest.test

{color:#d04437}_Javadoc_{color} [[tests 0 BuildFailureOnMessage |https://ci.ignite.apache.org/viewLog.html?buildId=3306859]]

[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3305204&amp;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
> 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
> We have to record the event contains all values and the chosen one.

This message was sent by Atlassian JIRA

View raw message