[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-07-08 Thread Anton Vinogradov (JIRA)


 [ 
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}Cache 6{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4289537]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4289583buildTypeId=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: 17h 50m
>  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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-07-08 Thread Anton Vinogradov (JIRA)


 [ 
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}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4257936]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4257321buildTypeId=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: 17h 50m
>  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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-07-04 Thread Anton Vinogradov (JIRA)


 [ 
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: No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4220768buildTypeId=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: 17h 50m
>  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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-07-01 Thread Anton Vinogradov (JIRA)


 [ 
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: No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4220768buildTypeId=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: 17h 50m
>  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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-07-01 Thread Anton Vinogradov (JIRA)


 [ 
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: No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4214540buildTypeId=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: 17h 50m
>  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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-06-28 Thread Anton Vinogradov (JIRA)


 [ 
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}Data Structures{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4219821]]

{color:#d04437}Cache 3{color} [[tests 
5|https://ci.ignite.apache.org/viewLog.html?buildId=4219823]]
* IgniteBinaryObjectsCacheTestSuite3: 
IgniteCacheGroupsTest.testLoadCacheAtomicPartitioned
* IgniteBinaryObjectsCacheTestSuite3: 
IgniteCacheGroupsTest.testLoadCacheAtomicReplicated
* IgniteBinaryObjectsCacheTestSuite3: 
IgniteCacheGroupsTest.testEntriesTtlAtomicReplicated
* IgniteBinaryObjectsCacheTestSuite3: IgniteTxGetAfterStopTest.testReplicated

{color:#d04437}Basic 1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=4219997]]
* IgniteBasicTestSuite: 
IgniteMarshallerCacheConcurrentReadWriteTest.testConcurrentReadWrite

{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4218803]]

{color:#d04437}Hibernate 5.1{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=4220003]]
* IgniteHibernate5TestSuite: 
HibernateL2CacheTransactionalUseSyncSelfTest.testNaturalIdCache
* IgniteHibernate5TestSuite: 
HibernateL2CacheTransactionalSelfTest.testNaturalIdCache

{color:#d04437}Hibernate 4.2{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=4220005]]
* IgniteHibernateTestSuite: 
HibernateL2CacheTransactionalSelfTest.testNaturalIdCache
* IgniteHibernateTestSuite: 
HibernateL2CacheTransactionalUseSyncSelfTest.testNaturalIdCache

{color:#d04437}Hibernate 5.3{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=4220007]]
* IgniteHibernate53TestSuite: 
HibernateL2CacheTransactionalUseSyncSelfTest.testNaturalIdCache
* IgniteHibernate53TestSuite: 
HibernateL2CacheTransactionalSelfTest.testNaturalIdCache

{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4218813]]

{color:#d04437}Cache 5{color} [[tests 
13|https://ci.ignite.apache.org/viewLog.html?buildId=4220011]]
* IgniteCacheTestSuite5: 
CacheSerializableTransactionsTest.testTxConflictReadEntryRemove1
* IgniteCacheTestSuite5: 
CacheSerializableTransactionsTest.testIncrementTxMultipleNodeRestart
* IgniteCacheTestSuite5: CacheLateAffinityAssignmentTest.testNoForceKeysRequests
* IgniteCacheTestSuite5: CacheSerializableTransactionsTest.testIncrementTx1
* IgniteCacheWithIndexingTestSuite: 
CacheBinaryKeyConcurrentQueryTest.testPutAndQueries
* IgniteCacheTestSuite5: CacheSerializableTransactionsTest.testTxConflictRead1
* IgniteCacheTestSuite5: 
CacheSerializableTransactionsTest.testTxConflictReadWrite3
* IgniteCacheTestSuite5: 
CacheSerializableTransactionsTest.testTxConflictReadEntry1
* IgniteCacheTestSuite5: 
CacheSerializableTransactionsTest.testTxConflictReadRemove1

{color:#d04437}Cache 1{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=4219841]]
* IgniteBinaryCacheTestSuite: 
IgniteCacheAtomicInvokeTest.testInvokeAllAppliedOnceOnBinaryTypeRegistration
* IgniteBinaryCacheTestSuite: 
GridCacheOffHeapAtomicMultiThreadedUpdateSelfTest.testPutGet
* IgniteBinaryCacheTestSuite: IgniteCacheTransactionalStopBusySelfTest.testGet
* IgniteBinaryCacheTestSuite: IgniteCacheAtomicStopBusySelfTest.testGet

{color:#d04437}Cache (Restarts) 1{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4219843]]

{color:#d04437}Continuous Query 3{color} [[tests 
5|https://ci.ignite.apache.org/viewLog.html?buildId=4220017]]
* IgniteCacheQuerySelfTestSuite5: 
CacheContinuousQueryOperationFromCallbackTest.testAtomicOneBackup
* IgniteCacheQuerySelfTestSuite5: 
CacheContinuousQueryOperationFromCallbackTest.testAtomicTwoBackups
* IgniteCacheQuerySelfTestSuite5: 
CacheContinuousQueryOperationFromCallbackTest.testTxTwoBackupsFilterPrimary
* IgniteCacheQuerySelfTestSuite5: 
CacheContinuousQueryOperationFromCallbackTest.testTxReplicatedFilter
* IgniteCacheQuerySelfTestSuite5: 
CacheContinuousQueryOperationFromCallbackTest.testTxTwoBackupsFilter

{color:#d04437}Continuous Query 4{color} [[tests 
10|https://ci.ignite.apache.org/viewLog.html?buildId=4220019]]
* IgniteCacheQuerySelfTestSuite6: 
CacheContinuousQueryOrderingEventTest.testTxOnheapTwoBackup
* IgniteCacheQuerySelfTestSuite6: 
CacheContinuousQueryAsyncFilterListenerTest.testNonDeadLockInFilterAtomicJCacheApi
* IgniteCacheQuerySelfTestSuite6: 
CacheContinuousQueryOrderingEventTest.testAtomicOnheapTwoBackup
* IgniteCacheQuerySelfTestSuite6: 
CacheContinuousQueryOrderingEventTest.testTxOnheapTwoBackupAsync
* IgniteCacheQuerySelfTestSuite6: 

[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-06-28 Thread Anton Vinogradov (JIRA)


 [ 
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}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4218670]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4214540buildTypeId=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: 17h 50m
>  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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-06-28 Thread Anton Vinogradov (JIRA)


 [ 
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}PDS (Indexing){color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4214505]]

{color:#d04437}MVCC Queries{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=4214474]]
* IgniteCacheMvccSqlTestSuite: 
CacheMvccReplicatedSqlQueriesTest.testAccountsTxSql_SingleNode_Persistence

{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4214906]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4214540buildTypeId=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: 17h 50m
>  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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-06-28 Thread Anton Vinogradov (JIRA)


 [ 
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: No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4171259buildTypeId=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: 17h 50m
>  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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-06-24 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET (Core Linux){color} [[tests 1 TIMEOUT 
|https://ci.ignite.apache.org/viewLog.html?buildId=4162135]]

{color:#d04437}Platform .NET{color} [[tests 2 TIMEOUT 
|https://ci.ignite.apache.org/viewLog.html?buildId=4162137]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4156884buildTypeId=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: 17h 50m
>  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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-06-20 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET (Core Linux){color} [[tests 1 TIMEOUT 
|https://ci.ignite.apache.org/viewLog.html?buildId=4162135]]

{color:#d04437}Platform .NET{color} [[tests 2 TIMEOUT 
|https://ci.ignite.apache.org/viewLog.html?buildId=4162137]]

{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4162140]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4156884buildTypeId=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: 17h 50m
>  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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-06-20 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET (Core Linux){color} [[tests 2 TIMEOUT 
|https://ci.ignite.apache.org/viewLog.html?buildId=4156856]]

{color:#d04437}Platform .NET{color} [[tests 2 TIMEOUT 
|https://ci.ignite.apache.org/viewLog.html?buildId=4156855]]

{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4157862]]

{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=4157863]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4156884buildTypeId=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: 17h 50m
>  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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-06-20 Thread Anton Vinogradov (JIRA)


 [ 
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}Interceptor Cache (Full API Config Variations / Basic)*{color} 
[[tests 208|https://ci.ignite.apache.org/viewLog.html?buildId=4155211]]
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_24.testGetAndPutIfAbsent
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_0.testPutxIfAbsentAsyncNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_76.testPutxIfAbsentAsyncOldNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_48.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_24.testRemoveAllSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_62.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_76.testGetAndPutIfAbsent
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_52.testPutxIfAbsentAsyncNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_28.testWithSkipStoreRemoveAll
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_0.testPutxIfAbsentAsyncOldNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_17.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_76.testRemoveAllSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_0.testGetAndPutIfAbsent
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_52.testPutxIfAbsentAsyncOldNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_73.testWithSkipStoreRemoveAll
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_24.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_0.testRemoveAllSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_87.testWithSkipStoreRemoveAll
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_38.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_52.testGetAndPutIfAbsent
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_28.testPutxIfAbsentAsyncNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_4.testWithSkipStoreRemoveAll
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_76.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_52.testRemoveAllSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_28.testPutxIfAbsentAsyncOldNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_73.testPutxIfAbsentAsyncNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_49.testWithSkipStoreRemoveAll
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_0.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_87.testPutxIfAbsentAsyncNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_63.testWithSkipStoreRemoveAll
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_14.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_73.testRemoveAllSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_28.testGetAndPutIfAbsent
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_4.testPutxIfAbsentAsyncNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_52.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_73.testPutxIfAbsentAsyncOldNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 

[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-06-19 Thread Anton Vinogradov (JIRA)


 [ 
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: #PR 5656 

{panel:title=-- Run :: All: Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Data Structures{color} [[tests 0 TIMEOUT , Exit Code , 
xmlReportParsingSurefireParsingFailure 
|https://ci.ignite.apache.org/viewLog.html?buildId=3988220]]

{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3988223]]

{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric 
|https://ci.ignite.apache.org/viewLog.html?buildId=3988227]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3981818buildTypeId=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: 17h 50m
>  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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-06-19 Thread Anton Vinogradov (JIRA)


 [ 
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}Interceptor Cache (Full API Config Variations / Basic)*{color} 
[[tests 208|https://ci.ignite.apache.org/viewLog.html?buildId=4140360]]
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_24.testGetAndPutIfAbsent
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_0.testPutxIfAbsentAsyncNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_76.testPutxIfAbsentAsyncOldNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_48.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_24.testRemoveAllSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_62.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_76.testGetAndPutIfAbsent
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_52.testPutxIfAbsentAsyncNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_28.testWithSkipStoreRemoveAll
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_0.testPutxIfAbsentAsyncOldNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_17.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_76.testRemoveAllSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_0.testGetAndPutIfAbsent
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_52.testPutxIfAbsentAsyncOldNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_73.testWithSkipStoreRemoveAll
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_24.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_0.testRemoveAllSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_87.testWithSkipStoreRemoveAll
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_38.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_52.testGetAndPutIfAbsent
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_28.testPutxIfAbsentAsyncNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_4.testWithSkipStoreRemoveAll
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_76.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_52.testRemoveAllSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_28.testPutxIfAbsentAsyncOldNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_73.testPutxIfAbsentAsyncNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_49.testWithSkipStoreRemoveAll
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_0.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_87.testPutxIfAbsentAsyncNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_63.testWithSkipStoreRemoveAll
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_14.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_73.testRemoveAllSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_28.testGetAndPutIfAbsent
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_4.testPutxIfAbsentAsyncNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_52.testWithSkipStore
* InterceptorCacheConfigVariationsFullApiTestSuite: 
InterceptorCacheConfigVariationsFullApiTest_73.testPutxIfAbsentAsyncOldNoTx
* InterceptorCacheConfigVariationsFullApiTestSuite: 

[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-05-30 Thread Anton Vinogradov (JIRA)


 [ 
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: #PR with readRepair enabled for each get!

Ignore this :) 

{panel:title=-- Run :: All: Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 30 TIMEOUT 
|https://ci.ignite.apache.org/viewLog.html?buildId=3988786]]
* exe: CacheAbstractTest.TestReplacex
* exe: CacheAbstractTest.TestGetAndReplace
* exe: CacheAbstractTest.TestContainsKey
* exe: CacheAbstractTransactionalTest.TestTransactionScopeAllOperations
* exe: CacheAbstractTest.TestRemovex
* exe: CacheAbstractTest.TestGetAndPut
* exe: CacheAbstractTransactionalTest.TestTransactionScopeAllOperations
* exe: CacheAbstractTest.TestInvoke
* exe: CacheAbstractTest.TestGetAndPutIfAbsent
* exe: CacheAbstractTest.TestClearKey
* exe: CacheAbstractTest.TestGetAndPut
* exe: CacheAbstractTest.TestGetAndPutIfAbsent
* exe: CacheAbstractTest.TestInvoke
* exe: CachePartitionedAtomicTest.TestPutIfAbsent(False)
* exe: CacheAbstractTest.TestRemovex
* exe: CacheAbstractTest.TestReplace
* exe: CacheAbstractTest.TestReplace
* exe: CacheAbstractTest.TestRemove
* exe: CacheAbstractTest.TestGetAndRemove
* exe: CacheAbstractTransactionalTest.TestTxDeadlockDetection
* exe: CacheAbstractTest.TestReplacex
* exe: CacheAbstractTest.TestClearKey
* exe: CacheAbstractTest.TestRemove
* exe: CacheAbstractTest.TestGetAndReplace
* exe: CacheAbstractTest.TestContainsKey
* exe: CacheAbstractTest.TestGetAndRemove
* exe: CachePartitionedTest.TestPutIfAbsent(False)

{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3988790]]

{color:#d04437}Cache 6{color} [[tests 
26|https://ci.ignite.apache.org/viewLog.html?buildId=3988765]]
* IgniteCacheTestSuite6: TxRollbackOnTimeoutTest.testSimple
* IgniteCacheTestSuite6: 
IgniteOptimisticTxSuspendResumeTest.testCrossCacheTxInAnotherThread
* IgniteCacheTestSuite6: 
ReplicatedAtomicCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6: 
ReplicatedAtomicCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6: 
IgniteOptimisticTxSuspendResumeTest.testSuspendTxAndStartNew
* IgniteCacheTestSuite6: 
IgniteOptimisticTxSuspendResumeTest.testSuspendTxAndStartNewWithoutCommit
* IgniteCacheTestSuite6: IgniteOptimisticTxSuspendResumeTest.testTxRollback
* IgniteCacheTestSuite6: IgniteOptimisticTxSuspendResumeTest.testResumeActiveTx
* IgniteCacheTestSuite6: transactions.TxRollbackOnTopologyChangeTest
* IgniteCacheTestSuite6: 
ReplicatedTransactionalOptimisticCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6: 
ReplicatedTransactionalOptimisticCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6: TxRollbackOnTimeoutNoDeadlockDetectionTest.testSimple
* IgniteCacheTestSuite6: 
ReplicatedTransactionalPessimisticCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6: 
ReplicatedTransactionalPessimisticCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6: 
IgniteOptimisticTxSuspendResumeTest.testResumeTxInAnotherThread
* IgniteCacheTestSuite6: 
PartitionedAtomicCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6: 
PartitionedAtomicCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6: 
TxRollbackOnTimeoutNearCacheTest.testLockAndConcurrentTimeout
* IgniteCacheTestSuite6: 
PartitionedTransactionalOptimisticCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6: 
PartitionedTransactionalOptimisticCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6: 
TxRollbackOnTopologyChangeTest.testRollbackOnTopologyChange
* IgniteCacheTestSuite6: 
PartitionedTransactionalPessimisticCacheGetsDistributionTest.testGetAllRequestsDistribution
* IgniteCacheTestSuite6: 
PartitionedTransactionalPessimisticCacheGetsDistributionTest.testGetRequestsDistribution
* IgniteCacheTestSuite6: 
TxOptimisticOnPartitionExchangeTest.testConsistencyOnPartitionExchange

{color:#d04437}PDS 4{color} [[tests 
3|https://ci.ignite.apache.org/viewLog.html?buildId=3988781]]
* IgnitePdsTestSuite4: 
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCacheAndCacheGroupSecondGroup

{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3988761]]

{color:#d04437}MVCC PDS 2{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=3988806]]
* IgnitePdsMvccTestSuite2: 
LocalWalModeChangeDuringRebalancingSelfTest.testDataClearedAfterRestartWithDisabledWal

{color:#d04437}Platform .NET{color} [[tests 58 TIMEOUT 
|https://ci.ignite.apache.org/viewLog.html?buildId=3988782]]
* exe: CacheTest.TestClearAll
* 

[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-05-30 Thread Anton Vinogradov (JIRA)


 [ 
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}Data Structures{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=3981399]]
* IgniteCacheDataStructuresSelfTestSuite: 
ReplicatedImplicitTransactionalCacheConsistencyTest.test[getEntry=true, 
async=true]
* IgniteCacheDataStructuresSelfTestSuite: 
ReplicatedImplicitTransactionalCacheConsistencyTest.test[getEntry=true, 
async=false]
* IgniteCacheDataStructuresSelfTestSuite: 
ReplicatedImplicitTransactionalCacheConsistencyTest.test[getEntry=false, 
async=true]
* IgniteCacheDataStructuresSelfTestSuite: 
ReplicatedImplicitTransactionalCacheConsistencyTest.test[getEntry=false, 
async=false]

{color:#d04437}Scala (Visor Console){color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3981740]]

{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3981817]]

{color:#d04437}PDS (Indexing){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3981403]]
* IgnitePdsWithIndexingCoreTestSuite: 
IgnitePdsAtomicCacheHistoricalRebalancingTest.testForceRebalanceClientTopology

{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Failure on metric 
|https://ci.ignite.apache.org/viewLog.html?buildId=3981791]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3981818buildTypeId=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.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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-05-27 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=3934727]]
* exe: CacheParityTest.TestCache

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3934728]]
* dll: CacheParityTest.TestCache

{color:#d04437}SPI (URI Deploy){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3934673]]
* IgniteUriDeploymentTestSuite: 
GridUriDeploymentSimpleSelfTest.testSimpleRedeployTwoTasks

{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3934755]]

{color:#d04437}Basic 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3934684]]
* IgniteBasicTestSuite: GridVersionSelfTest.testVersions

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3934756buildTypeId=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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-05-27 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=3946025]]
* exe: CacheParityTest.TestCache

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3946026]]
* dll: CacheParityTest.TestCache

{color:#d04437}PDS 4{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3947224]]

{color:#d04437}Data Structures{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=3946069]]
* IgniteCacheDataStructuresSelfTestSuite: 
GridCachePartitionedSetSelfTest.testMultithreaded

{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3946053]]

{color:#d04437}Cache 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3946110]]
* IgniteBinaryCacheTestSuite: 
GridCacheJdbcBlobStoreMultithreadedSelfTest.testMultithreadedExplicitTx

{color:#d04437}Cassandra Store{color} [[tests 
6|https://ci.ignite.apache.org/viewLog.html?buildId=3946052]]
* IgniteCassandraStoreTestSuite: IgnitePersistentStoreTest.loadCacheTest

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3946054buildTypeId=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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-05-25 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET{color} [[tests 
8|https://ci.ignite.apache.org/viewLog.html?buildId=3894167]]
* exe: CacheParityTest.TestCache

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3894168]]
* dll: CacheParityTest.TestCache

{color:#d04437}MVCC PDS 4{color} [[tests 
6|https://ci.ignite.apache.org/viewLog.html?buildId=3894193]]
* IgnitePdsMvccTestSuite4: 
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCacheAndCacheGroupSecondGroup
* IgnitePdsMvccTestSuite4: 
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testStopCachesOnDeactivationSecondGroup

{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3894195]]

{color:#d04437}Thin client: PHP{color} [[tests 104 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3894131]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3894196buildTypeId=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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-05-21 Thread Anton Vinogradov (JIRA)


 [ 
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=3491169buildTypeId=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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-05-17 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET{color} [[tests 
14|https://ci.ignite.apache.org/viewLog.html?buildId=3856482]]
* exe: CacheParityTest.TestCache

{color:#d04437}Platform C++ (Linux)*{color} [[tests 504 JVM CRASH , Exit Code , 
Failure on metric |https://ci.ignite.apache.org/viewLog.html?buildId=3856436]]

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3856483]]
* dll: CacheParityTest.TestCache

{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0 JVM CRASH , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3856434]]

{color:#d04437}ZooKeeper (Discovery) 2{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=3856435]]
* ZookeeperDiscoverySpiTestSuite2: GridCommandHandlerTest.testCacheIdleVerify
* ZookeeperDiscoverySpiTestSuite2: GridCommandHandlerTest.testTransactionInfo

{color:#d04437}Cache 8{color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=3856467]]
* IgniteCacheTestSuite8: 
SortedEvictionPolicySelfTest.testMaxSizeAllowEmptyEntries
* IgniteCacheTestSuite8: 
SortedEvictionPolicySelfTest.testMaxSizePartitionedNearDisabledWithBatch

{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3856510]]

{color:#d04437}Cache 3{color} [[tests 0 JVM CRASH , Out Of Memory Error , Exit 
Code |https://ci.ignite.apache.org/viewLog.html?buildId=3856462]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3856511buildTypeId=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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-04-22 Thread Anton Vinogradov (JIRA)


 [ 
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}Cache 2{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3663668]]

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3663673]]

{color:#d04437}Platform .NET{color} [[tests 152 TIMEOUT 
|https://ci.ignite.apache.org/viewLog.html?buildId=3663670]]
* exe: PartitionLossTest.TestReadOnlyAll - 75,1% fails in last 193 master runs.
* exe: PartitionLossTest.TestReadWriteAll - 66,3% fails in last 193 master runs.
* exe: PartitionLossTest.TestReadWriteSafe - 64,8% fails in last 193 master 
runs.
* exe: PartitionLossTest.TestReadOnlySafe - 63,7% fails in last 193 master runs.
* exe: CacheTest.TestAsyncCompletionOrder - 6,2% fails in last 193 master runs.
* exe: CacheTest.TestCacheNames - 5,7% fails in last 193 master runs.
* exe: ClientConnectionTest.TestAuthentication - 3,6% fails in last 193 master 
runs.
* exe: CacheTestSsl.TestPutGetUserObjects(False) - 3,1% fails in last 193 
master runs.
* exe: CacheTestKeepBinary.TestPutGetUserObjects(False) - 3,1% fails in last 
193 master runs.
* exe: CacheTest.TestClearAll - 3,1% fails in last 193 master runs.
* exe: SqlQueryTest.TestDml - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestClearKey - 3,1% fails in last 193 master runs.
* exe: CacheTestKeepBinary.TestPutIfAbsent - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestContainsKey - 3,1% fails in last 193 master runs.
* exe: CreateCacheTest.TestCreateFromConfiguration - 3,1% fails in last 193 
master runs.
* exe: CacheTest.TestContainsKeys - 3,1% fails in last 193 master runs.
* exe: CacheTestKeepBinary.TestRemove - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestExceptions - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestGetAll - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestGetAndPut - 3,1% fails in last 193 master runs.
* exe: SqlQueryTest.TestFieldsQuery - 3,1% fails in last 193 master runs.
* exe: SqlQueryTest.TestFieldsQueryCustomSchema - 3,1% fails in last 193 master 
runs.
* exe: SqlQueryTest.TestFieldsQueryDistributedJoins - 3,1% fails in last 193 
master runs.
* exe: SqlQueryTest.TestFieldsQueryMissingCache - 3,1% fails in last 193 master 
runs.
* exe: SqlQueryTest.TestFieldsQueryTimeout - 3,1% fails in last 193 master runs.
* exe: SqlQueryTest.TestSqlQuery - 3,1% fails in last 193 master runs.
* exe: SqlQueryTest.TestSqlQueryDistributedJoins - 3,1% fails in last 193 
master runs.
* exe: CacheTest.TestGetAsync - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestGetSize - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestPutAll - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestPutGetEmptyObject - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestPutGetPrimitives - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestPutIfAbsent - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestRemove - 3,1% fails in last 193 master runs.
* exe: CacheTestKeepBinary.TestRemoveReys - 3,1% fails in last 193 master runs.
* exe: ClientConnectionTest.TestEndPoints - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestGetAndPutIfAbsent - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestGetAndRemove - 3,1% fails in last 193 master runs.
* exe: ClientConnectionTest.TestFailover - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestGetAndReplace - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestGetAsync - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestGetSize - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestPutAll - 3,1% fails in last 193 master runs.
* exe: BinaryBuilderTest.TestClasslessBuilder - 3,1% fails in last 193 master 
runs.
* exe: BinaryBuilderTest.TestEnumBuilder - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestPutGetDictionary(True) - 3,1% fails in last 193 master 
runs.
* exe: CacheTest.TestPutGetDictionary(False) - 3,1% fails in last 193 master 
runs.
* exe: CreateCacheTest.TestCreateFromPartialConfiguration - 3,1% fails in last 
193 master runs.
* exe: CreateCacheTest.TestCreateFromTemplate - 3,1% fails in last 193 master 
runs.
* exe: BinaryBuilderTest.TestGetBinaryTypes - 3,1% fails in last 193 master 
runs.
* exe: BinaryBuilderTest.TestPersonBuilder - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestRemoveAll - 3,1% fails in last 193 master runs.
* exe: CreateCacheTest.TestGetCacheNames - 3,1% fails in last 193 master runs.
* exe: CacheTestKeepBinary.TestReplace - 3,1% fails in last 193 master runs.
* exe: CacheTest.TestRemoveKeyVal - 3,1% fails in last 193 master runs.
* exe: 

[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-04-21 Thread Anton Vinogradov (JIRA)


 [ 
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}Cache 2{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3650420]]

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3650442]]

{color:#d04437}Platform .NET{color} [[tests 151 TIMEOUT 
|https://ci.ignite.apache.org/viewLog.html?buildId=3650441]]
* exe: PartitionLossTest.TestReadOnlyAll - 77,0% fails in last 200 master runs.
* exe: PartitionLossTest.TestReadWriteSafe - 64,5% fails in last 200 master 
runs.
* exe: PartitionLossTest.TestReadOnlySafe - 64,0% fails in last 200 master runs.
* exe: CacheTest.TestAsyncCompletionOrder - 6,5% fails in last 200 master runs.
* exe: CacheTest.TestCacheNames - 5,5% fails in last 200 master runs.
* exe: ClientConnectionTest.TestAuthentication - 3,5% fails in last 200 master 
runs.
* exe: CacheTestSsl.TestPutGetUserObjects(False) - 3,0% fails in last 200 
master runs.
* exe: CacheTestKeepBinary.TestPutGetUserObjects(False) - 3,0% fails in last 
200 master runs.
* exe: CacheTest.TestClearAll - 3,0% fails in last 200 master runs.
* exe: SqlQueryTest.TestDml - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestClearKey - 3,0% fails in last 200 master runs.
* exe: CacheTestKeepBinary.TestPutIfAbsent - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestContainsKey - 3,0% fails in last 200 master runs.
* exe: CreateCacheTest.TestCreateFromConfiguration - 3,0% fails in last 200 
master runs.
* exe: CacheTest.TestContainsKeys - 3,0% fails in last 200 master runs.
* exe: CacheTestKeepBinary.TestRemove - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestExceptions - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestGetAll - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestGetAndPut - 3,0% fails in last 200 master runs.
* exe: SqlQueryTest.TestFieldsQuery - 3,0% fails in last 200 master runs.
* exe: SqlQueryTest.TestFieldsQueryCustomSchema - 3,0% fails in last 200 master 
runs.
* exe: SqlQueryTest.TestFieldsQueryDistributedJoins - 3,0% fails in last 200 
master runs.
* exe: SqlQueryTest.TestFieldsQueryMissingCache - 3,0% fails in last 200 master 
runs.
* exe: SqlQueryTest.TestFieldsQueryTimeout - 3,0% fails in last 200 master runs.
* exe: SqlQueryTest.TestSqlQuery - 3,0% fails in last 200 master runs.
* exe: SqlQueryTest.TestSqlQueryDistributedJoins - 3,0% fails in last 200 
master runs.
* exe: CacheTest.TestGetAsync - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestGetSize - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestPutAll - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestPutGetEmptyObject - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestPutGetPrimitives - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestPutIfAbsent - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestRemove - 3,0% fails in last 200 master runs.
* exe: CacheTestKeepBinary.TestRemoveReys - 3,0% fails in last 200 master runs.
* exe: ClientConnectionTest.TestEndPoints - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestGetAndPutIfAbsent - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestGetAndRemove - 3,0% fails in last 200 master runs.
* exe: ClientConnectionTest.TestFailover - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestGetAndReplace - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestGetAsync - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestGetSize - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestPutAll - 3,0% fails in last 200 master runs.
* exe: BinaryBuilderTest.TestClasslessBuilder - 3,0% fails in last 200 master 
runs.
* exe: BinaryBuilderTest.TestEnumBuilder - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestPutGetDictionary(True) - 3,0% fails in last 200 master 
runs.
* exe: CacheTest.TestPutGetDictionary(False) - 3,0% fails in last 200 master 
runs.
* exe: CreateCacheTest.TestCreateFromPartialConfiguration - 3,0% fails in last 
200 master runs.
* exe: CreateCacheTest.TestCreateFromTemplate - 3,0% fails in last 200 master 
runs.
* exe: BinaryBuilderTest.TestGetBinaryTypes - 3,0% fails in last 200 master 
runs.
* exe: BinaryBuilderTest.TestPersonBuilder - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestRemoveAll - 3,0% fails in last 200 master runs.
* exe: CreateCacheTest.TestGetCacheNames - 3,0% fails in last 200 master runs.
* exe: CacheTestKeepBinary.TestReplace - 3,0% fails in last 200 master runs.
* exe: CacheTest.TestRemoveKeyVal - 3,0% fails in last 200 master runs.
* exe: CreateCacheTest.TestGetOrCreateFromConfiguration - 3,0% fails in last 
200 master runs.
* exe: 

[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-04-19 Thread Anton Vinogradov (JIRA)


 [ 
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}Cache 2{color} [[tests 
125|https://ci.ignite.apache.org/viewLog.html?buildId=3648358]]
* IgniteCacheTestSuite2: cache.CacheOptimisticTransactionsWithFilterTest
* IgniteCacheTestSuite2: local.GridCacheLocalTxSingleThreadedSelfTest
* IgniteCacheTestSuite2: 
cache.CacheOptimisticTransactionsWithFilterSingleServerTest
* IgniteCacheTestSuite2: local.GridCacheLocalMultithreadedSelfTest
* IgniteCacheTestSuite2: local.GridCacheLocalLockSelfTest
* IgniteCacheTestSuite2: local.GridCacheLocalLoadAllSelfTest
* IgniteCacheTestSuite2: local.GridCacheLocalTxMultiThreadedSelfTest
* IgniteCacheTestSuite2: local.GridCacheLocalEvictionEventSelfTest
* IgniteCacheTestSuite2: local.GridCacheLocalEventSelfTest
* IgniteCacheTestSuite2: local.GridCacheLocalTxTimeoutSelfTest
* IgniteCacheTestSuite2: local.GridCacheLocalBasicApiSelfTest
* IgniteCacheTestSuite2: cache.CrossCacheTxRandomOperationsTest
* IgniteCacheTestSuite2: cache.CacheEnumOperationsTest
* IgniteCacheTestSuite2: local.GridCacheLocalAtomicGetAndTransformStoreSelfTest
* IgniteCacheTestSuite2: cache.CrossCacheTxNearEnabledRandomOperationsTest
* IgniteCacheTestSuite2: local.GridCacheLocalGetAndTransformStoreSelfTest
* IgniteCacheTestSuite2: cache.IgniteCacheNoSyncForGetTest
* IgniteCacheTestSuite2: local.GridCacheLocalAtomicBasicStoreSelfTest
* IgniteCacheTestSuite2: cache.IgniteCacheIncrementTxTest
* IgniteCacheTestSuite2: local.GridCacheLocalBasicStoreSelfTest
* IgniteCacheTestSuite2: near.GridCacheNearReaderPreloadSelfTest
* IgniteCacheTestSuite2: near.GridCacheNearReadersSelfTest
* IgniteCacheTestSuite2: near.GridCacheAtomicNearMultiNodeSelfTest
* IgniteCacheTestSuite2: near.GridCacheNearMultiNodeSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedBasicStoreSelfTest
* IgniteCacheTestSuite2: 
near.GridCachePartitionedAtomicGetAndTransformStoreSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedGetAndTransformStoreSelfTest
* IgniteCacheTestSuite2: near.GridCacheAtomicNearReadersSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedBasicApiTest
* IgniteCacheTestSuite2: cache.GridCachePartitionedGetSelfTest
* IgniteCacheTestSuite2: distributed.GridCacheTransformEventSelfTest
* IgniteCacheTestSuite2: local.GridCacheLocalIsolatedNodesSelfTest
* IgniteCacheTestSuite2: near.GridCacheNearOneNodeSelfTest
* IgniteCacheTestSuite2: near.NoneRebalanceModeSelfTest
* IgniteCacheTestSuite2: near.GridCacheNearMultiGetSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedBasicOpSelfTest
* IgniteCacheTestSuite2: distributed.CacheLockReleaseNodeLeaveTest
* IgniteCacheTestSuite2: 
near.GridCachePartitionedExplicitLockNodeFailureSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedNodeFailureSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedMultiThreadedPutGetSelfTest
* IgniteCacheTestSuite2: cache.GridCacheFinishPartitionsSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedTxTimeoutSelfTest
* IgniteCacheTestSuite2: dht.GridCacheColocatedTxSingleThreadedSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedTxSingleThreadedSelfTest
* IgniteCacheTestSuite2: cache.CacheConcurrentReadThroughTest
* IgniteCacheTestSuite2: 
near.GridCachePartitionedNearDisabledBasicStoreMultiNodeSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedBasicStoreMultiNodeSelfTest
* IgniteCacheTestSuite2: near.GridNearCacheStoreUpdateTest
* IgniteCacheTestSuite2: near.GridCachePartitionedMultiNodeSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedMultiNodeLockSelfTest
* IgniteCacheTestSuite2: dht.GridCachePartitionedNearDisabledLockSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedLockSelfTest
* IgniteCacheTestSuite2: near.GridCacheNearPreloadRestartSelfTest
* IgniteCacheTestSuite2: dht.GridCacheColocatedPreloadRestartSelfTest
* IgniteCacheTestSuite2: dht.GridCacheDhtPreloadMultiThreadedSelfTest
* IgniteCacheTestSuite2: dht.GridCacheDhtPreloadDisabledSelfTest
* IgniteCacheTestSuite2: dht.GridCacheDhtPreloadDelayedSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedPreloadLifecycleSelfTest
* IgniteCacheTestSuite2: dht.GridCacheDhtPreloadUnloadSelfTest
* IgniteCacheTestSuite2: dht.GridCacheDhtPreloadStartStopSelfTest
* IgniteCacheTestSuite2: dht.GridCacheDhtMappingSelfTest
* IgniteCacheTestSuite2: dht.GridCacheDhtEntrySelfTest
* IgniteCacheTestSuite2: 
distributed.GridCachePartitionedNearDisabledTxMultiThreadedSelfTest
* IgniteCacheTestSuite2: near.GridCachePartitionedTxMultiThreadedSelfTest
* IgniteCacheTestSuite2: dht.GridCacheDhtPreloadPutGetSelfTest
* IgniteCacheTestSuite2: dht.GridCacheDhtPreloadBigDataSelfTest
* IgniteCacheTestSuite2: dht.GridCacheDhtPreloadOnheapSelfTest
* 

[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-04-19 Thread Anton Vinogradov (JIRA)


 [ 
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}Cache 2{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3640831]]

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3640853]]

{color:#d04437}JDBC Driver{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3640789]]

{color:#d04437}Platform .NET{color} [[tests 
8|https://ci.ignite.apache.org/viewLog.html?buildId=3640852]]
* exe: CacheParityTest.TestCache - 0,0% fails in last 209 master runs.

{color:#d04437}Cache 5{color} [[tests 
5|https://ci.ignite.apache.org/viewLog.html?buildId=3640834]]
* IgniteCacheTestSuite5: 
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithPersistence[ATOMIC]
 - 0,0% fails in last 136 master runs.

{color:#d04437}PDS 4{color} [[tests 
3|https://ci.ignite.apache.org/viewLog.html?buildId=3640851]]
* IgnitePdsTestSuite4: 
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCachesInDifferentCacheGroupsFirstGroup
 - 0,0% fails in last 140 master runs.
* IgnitePdsTestSuite4: 
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCacheAndCacheGroupSecondGroup
 - 0,0% fails in last 140 master runs.

{color:#d04437}Activate / Deactivate Cluster{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3640771]]
* IgniteStandByClusterSuite: 
IgniteClusterActivateDeactivateTest.testActivateFailover3 - 0,0% fails in last 
140 master runs.

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

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3640882buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-04-03 Thread Anton Vinogradov (JIRA)


 [ 
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}ZooKeeper (Discovery) 2{color} [[tests 
5|https://ci.ignite.apache.org/viewLog.html?buildId=3491092]]
* ZookeeperDiscoverySpiTestSuite2: 
IgniteClientReconnectCacheTest.testTxStateAfterClientReconnect - 0,3% fails in 
last 349 master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteClientReconnectCacheTest.testReconnectMultinodeLongHistory - 0,0% fails 
in last 349 master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated - 0,0% 
fails in last 349 master runs.
* ZookeeperDiscoverySpiTestSuite2: 
IgniteClientReconnectCacheTest.testReconnectInitialExchangeInProgress - 0,0% 
fails in last 349 master runs.

{color:#d04437}Continuous Query 3{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3491127]]

{color:#d04437}Thin client: Node.js{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3491095]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3491169buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-04-03 Thread Anton Vinogradov (JIRA)


 [ 
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: No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3479508buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-04-02 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET (Core Linux){color} [[tests 0 Exit Code , 
TC_SERVICE_MESSAGE |https://ci.ignite.apache.org/viewLog.html?buildId=3488258]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3479508buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-04-02 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET (Core Linux){color} [[tests 0 Exit Code , 
TC_SERVICE_MESSAGE |https://ci.ignite.apache.org/viewLog.html?buildId=3482366]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3479508buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-04-02 Thread Anton Vinogradov (JIRA)


 [ 
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}ZooKeeper (Discovery) 1{color} [[tests 
122|https://ci.ignite.apache.org/viewLog.html?buildId=3479430]]
* ZookeeperDiscoverySpiTestSuite1: 
ZookeeperDiscoverySpiSaslSuccessfulAuthTest.testIgniteNodeWithoutSaslConfigurationSuccessfullyJoins
 - 0,0% fails in last 373 master runs.

{color:#d04437}Cassandra Store{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3479507]]
* IgniteCassandraStoreTestSuite: tests.IgnitePersistentStoreTest - 0,0% fails 
in last 0 master runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code , 
TC_SERVICE_MESSAGE |https://ci.ignite.apache.org/viewLog.html?buildId=3479479]]

{color:#d04437}Platform C++ (Linux Clang){color} [[tests 0 Exit Code , Failure 
on metric |https://ci.ignite.apache.org/viewLog.html?buildId=3479438]]

{color:#d04437}Thin client: Python{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3479485]]

{color:#d04437}Platform C++ (Win x64 | Release){color} [[tests 1 
BuildFailureOnMessage 
|https://ci.ignite.apache.org/viewLog.html?buildId=3479433]]
* IgniteOdbcTest: SslQueriesTestSuite: TestConnectionSslSuccess - 1,7% fails in 
last 786 master runs.

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3479508buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-04-01 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET{color} [[tests 0 Exit Code , Compilation Error 
|https://ci.ignite.apache.org/viewLog.html?buildId=3455486]]

{color:#d04437}Platform .NET (Long Running){color} [[tests 0 Exit Code , 
Compilation Error |https://ci.ignite.apache.org/viewLog.html?buildId=3455340]]

{color:#d04437}MVCC Queries{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3455299]]

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code , 
TC_SERVICE_MESSAGE |https://ci.ignite.apache.org/viewLog.html?buildId=3455337]]

{color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3455346]]

{color:#d04437}Thin client: PHP{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3455300]]

{color:#d04437}Thin client: Node.js{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3455292]]

{color:#d04437}Platform .NET (Integrations){color} [[tests 0 Exit Code , 
Compilation Error |https://ci.ignite.apache.org/viewLog.html?buildId=3455339]]

{color:#d04437}Thin client: Python{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3455343]]

{color:#d04437}Platform .NET (NuGet)*{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3455341]]

{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Exit Code , 
Compilation Error , Failure on metric 
|https://ci.ignite.apache.org/viewLog.html?buildId=3455338]]

{color:#d04437}MVCC PDS 2{color} [[tests 
3|https://ci.ignite.apache.org/viewLog.html?buildId=3455362]]
* IgnitePdsMvccTestSuite2: 
LocalWalModeChangeDuringRebalancingSelfTest.testWalNotDisabledIfParameterSetToFalse
 - 0,0% fails in last 353 master runs.

{color:#d04437}Queries 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=3455342]]
* IgniteBinaryCacheQueryTestSuite: 
IndexingCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithDelay[ATOMIC]
 - 0,0% fails in last 171 master runs.

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3455366buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-04-01 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET{color} [[tests 0 Exit Code , Compilation Error 
|https://ci.ignite.apache.org/viewLog.html?buildId=3452450]]

{color:#d04437}Platform .NET (Long Running){color} [[tests 0 Exit Code , 
Compilation Error |https://ci.ignite.apache.org/viewLog.html?buildId=3452453]]

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code , 
TC_SERVICE_MESSAGE |https://ci.ignite.apache.org/viewLog.html?buildId=3452457]]

{color:#d04437}Platform .NET (Integrations){color} [[tests 0 Exit Code , 
Compilation Error |https://ci.ignite.apache.org/viewLog.html?buildId=3452467]]

{color:#d04437}Platform .NET (NuGet)*{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3452471]]

{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Exit Code , 
Compilation Error , Failure on metric 
|https://ci.ignite.apache.org/viewLog.html?buildId=3452473]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3445548buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-03-29 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET{color} [[tests 0 Exit Code , Compilation Error 
|https://ci.ignite.apache.org/viewLog.html?buildId=3445518]]

{color:#d04437}Platform .NET (Long Running){color} [[tests 0 Exit Code , 
Compilation Error |https://ci.ignite.apache.org/viewLog.html?buildId=3445522]]

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code , 
TC_SERVICE_MESSAGE |https://ci.ignite.apache.org/viewLog.html?buildId=3445519]]

{color:#d04437}PDS (Indexing){color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3445512]]

{color:#d04437}Spring{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3445459]]

{color:#d04437}Platform C++ (Linux Clang){color} [[tests 0 TIMEOUT , Exit Code 
, Failure on metric |https://ci.ignite.apache.org/viewLog.html?buildId=3445478]]

{color:#d04437}Platform C++ (Linux){color} [[tests 0 TIMEOUT , Exit Code , 
Failure on metric |https://ci.ignite.apache.org/viewLog.html?buildId=3445472]]

{color:#d04437}Platform .NET (Integrations){color} [[tests 0 Exit Code , 
Compilation Error |https://ci.ignite.apache.org/viewLog.html?buildId=3445521]]

{color:#d04437}Platform .NET (NuGet)*{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3445523]]

{color:#d04437}Platform .NET (Inspections)*{color} [[tests 0 Exit Code , 
Compilation Error , Failure on metric 
|https://ci.ignite.apache.org/viewLog.html?buildId=3445520]]

{color:#d04437}SPI (URI Deploy){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=3445464]]
* IgniteUriDeploymentTestSuite: 
GridUriDeploymentClassLoaderSelfTest.testNestedJarClassloading - 0,2% fails in 
last 403 master runs.
* IgniteUriDeploymentTestSuite: 
GridUriDeploymentClassLoaderSelfTest.testClasspathResourceLoading - 0,2% fails 
in last 403 master runs.
* IgniteUriDeploymentTestSuite: 
GridUriDeploymentMultiScannersSelfTest.testDeployment - 0,2% fails in last 403 
master runs.

{color:#d04437}PDS 4{color} [[tests 
7|https://ci.ignite.apache.org/viewLog.html?buildId=3445517]]
* IgnitePdsTestSuite4: 
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCacheAndCacheGroupFirstGroup
 - 0,0% fails in last 400 master runs.
* IgnitePdsTestSuite4: 
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCachesInDifferentCacheGroupsFirstGroup
 - 0,0% fails in last 400 master runs.
* IgnitePdsTestSuite4: 
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testDestroySpecificCachesInDifferentCacheGroupsSecondGroup
 - 0,0% fails in last 400 master runs.
* IgnitePdsTestSuite4: 
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testStopCachesOnDeactivationFirstGroup
 - 0,0% fails in last 400 master runs.
* IgnitePdsTestSuite4: 
ResetLostPartitionTest.testReactivateGridBeforeResetLostPartitions - 0,0% fails 
in last 400 master runs.
* IgnitePdsTestSuite4: ResetLostPartitionTest.testResetLostPartitions - 0,0% 
fails in last 400 master runs.
* IgnitePdsTestSuite4: 
IgniteRebalanceOnCachesStoppingOrDestroyingTest.testStopCachesOnDeactivationSecondGroup
 - 0,0% fails in last 400 master runs.

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3445548buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-03-29 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET{color} [[tests 0 Exit Code , Compilation Error 
|https://ci.ignite.apache.org/viewLog.html?buildId=3441587]]

{color:#d04437}Platform .NET (Core Linux){color} [[tests 0 Exit Code , 
TC_SERVICE_MESSAGE |https://ci.ignite.apache.org/viewLog.html?buildId=3441590]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3433512buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-03-28 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET{color} [[tests 
14|https://ci.ignite.apache.org/viewLog.html?buildId=3440563]]
* exe: CacheParityTest.TestCache - 0,0% fails in last 509 master runs.

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

{color:#d04437}_Licenses Headers_{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3440567]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3433512buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-03-28 Thread Anton Vinogradov (JIRA)


 [ 
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}Platform .NET{color} [[tests 
9|https://ci.ignite.apache.org/viewLog.html?buildId=3434964]]
* exe: CacheParityTest.TestCache - 0,0% fails in last 517 master runs.

{color:#d04437}MVCC PDS 1{color} [[tests 
9|https://ci.ignite.apache.org/viewLog.html?buildId=3433507]]
* IgnitePdsMvccTestSuite: 
DistributedMetaStoragePersistentTest.testJoinCleanNodeFullData - 0,0% fails in 
last 406 master runs.
* IgnitePdsMvccTestSuite: 
DistributedMetaStoragePersistentTest.testDeactivateActivate - 0,0% fails in 
last 406 master runs.
* IgnitePdsMvccTestSuite: 
DistributedMetaStoragePersistentTest.testMultipleNodes - 0,0% fails in last 406 
master runs.
* IgnitePdsMvccTestSuite: 
DistributedMetaStoragePersistentTest.testJoinCleanNode - 0,0% fails in last 406 
master runs.
* IgnitePdsMvccTestSuite: DistributedMetaStoragePersistentTest.testCas - 0,0% 
fails in last 406 master runs.
* IgnitePdsMvccTestSuite: 
DistributedMetaStoragePersistentTest.testListenersOnRemove - 0,0% fails in last 
406 master runs.
* IgnitePdsMvccTestSuite: 
DistributedMetaStoragePersistentTest.testJoinNodeWithLongerHistory - 0,0% fails 
in last 406 master runs.
* IgnitePdsMvccTestSuite: 
DistributedMetaStoragePersistentTest.testListenersOnWrite - 0,0% fails in last 
406 master runs.

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

{color:#d04437}_Licenses Headers_{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=3434970]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3433512buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-03-26 Thread Anton Vinogradov (JIRA)


 [ 
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}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]]

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3305204buildTypeId=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 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)


[jira] [Issue Comment Deleted] (IGNITE-10663) Implement cache mode allows reads with consistency check and fix

2019-03-14 Thread Anton Vinogradov (JIRA)


 [ 
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 :: IntelliJ IDEA Inspections: No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *- Run :: IntelliJ IDEA Inspections* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3305183buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections])

> 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 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)