[jira] [Updated] (IGNITE-5935) MVCC TX: Tx recovery protocol

2018-10-19 Thread Ivan Pavlukhin (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Pavlukhin updated IGNITE-5935:
---
Attachment: 
mtcga.gridgain.com_build.html_serverId=apache=true=2111226=Check.png

> MVCC TX: Tx recovery protocol
> -
>
> Key: IGNITE-5935
> URL: https://issues.apache.org/jira/browse/IGNITE-5935
> Project: Ignite
>  Issue Type: Task
>  Components: cache, mvcc
>Reporter: Semen Boikov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.7
>
> Attachments: 
> mtcga.gridgain.com_build.html_serverId=apache=true=2111226=Check.png
>
>
> Transaction recovery procedure is initiated when near node failed before 
> transaction was finished.
> In MVCC transactions _partition update counter_ modification is started on 
> prepare phase. If a transaction was prepared at least on one node we need to 
> finish _partition update counter_ modification consistently on all 
> participating nodes.
> Also recovered transaction should be removed from active transactions list on 
> mvcc coordinator.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (IGNITE-5935) MVCC TX: Tx recovery protocol

2018-09-26 Thread Ivan Pavlukhin (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Pavlukhin updated IGNITE-5935:
---
Description: 
Transaction recovery procedure is initiated when near node failed before 
transaction was finished.
In MVCC transactions _partition update counter_ modification is started on 
prepare phase. If a transaction was prepared at least on one node we need to 
finish _partition update counter_ modification consistently on all 
participating nodes.
Also recovered transaction should be removed from active transactions list on 
mvcc coordinator.

  was:
Transaction recovery procedure is initiated when near node failed before 
transaction was finished.
In MVCC transactions _partition update counter_ modification is started on 
prepare phase. If a transaction was prepared at least on one node we need to 
finish _partition update counter_ modification consistently on all 
participating nodes.


> MVCC TX: Tx recovery protocol
> -
>
> Key: IGNITE-5935
> URL: https://issues.apache.org/jira/browse/IGNITE-5935
> Project: Ignite
>  Issue Type: Task
>  Components: cache, mvcc
>Reporter: Semen Boikov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.7
>
>
> Transaction recovery procedure is initiated when near node failed before 
> transaction was finished.
> In MVCC transactions _partition update counter_ modification is started on 
> prepare phase. If a transaction was prepared at least on one node we need to 
> finish _partition update counter_ modification consistently on all 
> participating nodes.
> Also recovered transaction should be removed from active transactions list on 
> mvcc coordinator.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (IGNITE-5935) MVCC TX: Tx recovery protocol

2018-09-25 Thread Ivan Pavlukhin (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Pavlukhin updated IGNITE-5935:
---
Description: 
Transaction recovery procedure is initiated when near node failed before 
transaction was finished.
In MVCC transactions _partition update counter_ modification is started on 
prepare phase. If a transaction was prepared at least on one node we need to 
finish _partition update counter_ modification consistently on all 
participating nodes.

  was:
Tx recovery doesn't work properly for txs over MVCC enabled caches using Cache 
API. It requires MvccSnapshot which may not be acquired at recovery time.
Need to implement logic for checking whether snapshot was already gotten by one 
of tx participants and use existing one, request and spread between 
participants a new snapshot otherwise.


> MVCC TX: Tx recovery protocol
> -
>
> Key: IGNITE-5935
> URL: https://issues.apache.org/jira/browse/IGNITE-5935
> Project: Ignite
>  Issue Type: Task
>  Components: cache, mvcc
>Reporter: Semen Boikov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.7
>
>
> Transaction recovery procedure is initiated when near node failed before 
> transaction was finished.
> In MVCC transactions _partition update counter_ modification is started on 
> prepare phase. If a transaction was prepared at least on one node we need to 
> finish _partition update counter_ modification consistently on all 
> participating nodes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (IGNITE-5935) MVCC TX: Tx recovery protocol

2018-08-17 Thread Igor Seliverstov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor Seliverstov updated IGNITE-5935:
-
Description: 
Tx recovery doesn't work properly for txs over MVCC enabled caches using Cache 
API. It requires MvccSnapshot which may not be acquired at recovery time.
Need to implement logic for checking whether snapshot was already gotten by one 
of tx participants and use existing one, request and spread between 
participants a new snapshot otherwise.

  was:
Need make sure tx recovery work properly with mvcc enabled:
- tx IDs are generated and not lost if transaction is committed by recovery 
procedure
- tx should be removed from list of active transactions on coordinator


> MVCC TX: Tx recovery protocol
> -
>
> Key: IGNITE-5935
> URL: https://issues.apache.org/jira/browse/IGNITE-5935
> Project: Ignite
>  Issue Type: Task
>  Components: cache, mvcc
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.7
>
>
> Tx recovery doesn't work properly for txs over MVCC enabled caches using 
> Cache API. It requires MvccSnapshot which may not be acquired at recovery 
> time.
> Need to implement logic for checking whether snapshot was already gotten by 
> one of tx participants and use existing one, request and spread between 
> participants a new snapshot otherwise.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (IGNITE-5935) MVCC TX: Tx recovery protocol

2018-08-17 Thread Igor Seliverstov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor Seliverstov updated IGNITE-5935:
-
Summary: MVCC TX: Tx recovery protocol  (was: Integrate mvcc support in tx 
recovery protocol)

> MVCC TX: Tx recovery protocol
> -
>
> Key: IGNITE-5935
> URL: https://issues.apache.org/jira/browse/IGNITE-5935
> Project: Ignite
>  Issue Type: Task
>  Components: cache, mvcc
>Reporter: Semen Boikov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.7
>
>
> Need make sure tx recovery work properly with mvcc enabled:
> - tx IDs are generated and not lost if transaction is committed by recovery 
> procedure
> - tx should be removed from list of active transactions on coordinator



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)