[jira] [Commented] (IGNITE-13873) Milti-cell transaction changes may be not visible (during some time) after the Cellular switch [Sync-free switch]

2021-06-29 Thread Alexey Gidaspov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17371672#comment-17371672
 ] 

Alexey Gidaspov commented on IGNITE-13873:
--

Hello [~av],
I see 'Release Notes Required' flag is set and no release note attached. Please 
add release note or remove the flag. Thank you. 
 

> Milti-cell transaction changes may be not visible (during some time) after 
> the Cellular switch [Sync-free switch]
> -
>
> Key: IGNITE-13873
> URL: https://issues.apache.org/jira/browse/IGNITE-13873
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Critical
>  Labels: iep-45
> Fix For: 2.11
>
> Attachments: master (as 2.9) vs improved (as dev) .png
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Transactions over some cells may be recovered after the stale data read.
> For example:
> We have 2 cells, the first contains partitions for k1, second for k2.
> Tx with put(k1,v1) and put(k2,v2) started and prepared.
> Then node from the first cell, which is the primary for k1, failed.
> Currently, the second cell (with key2) may finish the cellular switch before 
> tx recovered and stale data read is possible.
> Primaries from the {{tx.transactionNodes()}} should be taken into account 
> instead of the current logic that awaits for all transactions located on 
> nodes who are backups to the failed primary.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13873) Milti-cell transaction changes may be not visible (during some time) after the Cellular switch [Sync-free switch]

2021-04-02 Thread Anton Vinogradov (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313713#comment-17313713
 ] 

Anton Vinogradov commented on IGNITE-13873:
---

Merged into master.

> Milti-cell transaction changes may be not visible (during some time) after 
> the Cellular switch [Sync-free switch]
> -
>
> Key: IGNITE-13873
> URL: https://issues.apache.org/jira/browse/IGNITE-13873
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Critical
>  Labels: iep-45
> Fix For: 2.11
>
> Attachments: master (as 2.9) vs improved (as dev) .png
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Transactions over some cells may be recovered after the stale data read.
> For example:
> We have 2 cells, the first contains partitions for k1, second for k2.
> Tx with put(k1,v1) and put(k2,v2) started and prepared.
> Then node from the first cell, which is the primary for k1, failed.
> Currently, the second cell (with key2) may finish the cellular switch before 
> tx recovered and stale data read is possible.
> Primaries from the {{tx.transactionNodes()}} should be taken into account 
> instead of the current logic that awaits for all transactions located on 
> nodes who are backups to the failed primary.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (IGNITE-13873) Milti-cell transaction changes may be not visible (during some time) after the Cellular switch [Sync-free switch]

2021-04-01 Thread Ignite TC Bot (Jira)


[ 
https://issues.apache.org/jira/browse/IGNITE-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313271#comment-17313271
 ] 

Ignite TC Bot commented on IGNITE-13873:


{panel:title=Branch: [pull/8822/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8822/head] Base: [master] : New Tests 
(44)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 5{color} [[tests 
44|https://ci.ignite.apache.org/viewLog.html?buildId=5943668]]
* {color:#013220}IgniteCacheTestSuite5: 
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
 = OPTIMISTIC, Concurrency = READ_COMMITTED, Started from = BROKEN_CELL] - 
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: 
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
 = OPTIMISTIC, Concurrency = READ_COMMITTED, Started from = ALIVE_CELL] - 
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: 
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
 = OPTIMISTIC, Concurrency = READ_COMMITTED, Started from = FAILED] - 
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: 
GridExchangeFreeCellularSwitchIsolationTest.testOnlyAffectedNodesWaitForRecovery[Started
 from = BROKEN_CELL] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: 
GridExchangeFreeCellularSwitchIsolationTest.testOnlyAffectedNodesWaitForRecovery[Started
 from = ALIVE_CELL] - PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: 
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
 = PESSIMISTIC, Concurrency = REPEATABLE_READ, Started from = BROKEN_CELL] - 
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: 
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
 = PESSIMISTIC, Concurrency = REPEATABLE_READ, Started from = ALIVE_CELL] - 
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: 
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
 = PESSIMISTIC, Concurrency = READ_COMMITTED, Started from = ALIVE_CELL] - 
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: 
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
 = PESSIMISTIC, Concurrency = REPEATABLE_READ, Started from = FAILED] - 
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: 
GridExchangeFreeCellularSwitchComplexOperationsTest.testComplexOperationsRecoveryOnCellularSwitch[Isolation
 = PESSIMISTIC, Concurrency = SERIALIZABLE, Started from = ALIVE_CELL] - 
PASSED{color}
* {color:#013220}IgniteCacheTestSuite5: 
GridExchangeFreeCellularSwitchIsolationTest.testOnlyAffectedNodesWaitForRecovery[Started
 from = FAILED] - PASSED{color}
... and 33 new tests

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5946627buildTypeId=IgniteTests24Java8_RunAll]

> Milti-cell transaction changes may be not visible (during some time) after 
> the Cellular switch [Sync-free switch]
> -
>
> Key: IGNITE-13873
> URL: https://issues.apache.org/jira/browse/IGNITE-13873
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Critical
>  Labels: iep-45
> Fix For: 2.11
>
> Attachments: master (as 2.9) vs improved (as dev) .png
>
>  Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Transactions over some cells may be recovered after the stale data read.
> For example:
> We have 2 cells, the first contains partitions for k1, second for k2.
> Tx with put(k1,v1) and put(k2,v2) started and prepared.
> Then node from the first cell, which is the primary for k1, failed.
> Currently, the second cell (with key2) may finish the cellular switch before 
> tx recovered and stale data read is possible.
> Primaries from the {{tx.transactionNodes()}} should be taken into account 
> instead of the current logic that awaits for all transactions located on 
> nodes who are backups to the failed primary.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)