ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-5714) Context switching for pessimistic transactions
Date Fri, 13 Oct 2017 09:43:00 GMT

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

Alexey Kuznetsov updated IGNITE-5714:
-------------------------------------
    Description: 
Support transaction suspend()\resume() operations for pessimistic transactions. Resume can
be called in another thread.

   _+But there is a problem+_: Imagine, we started pessimistic transaction in thread T1 and
then perform put operation, which leads to sending GridDistributedLockRequest to another node.
Lock request contains thread id of the transaction. Then we call suspend, resume in another
thread and we also must send messages to other nodes to change thread id. 

It seems complicated task.It’s better to get rid of sending thread id to the nodes.
We can use transaction xid on other nodes instead of thread id. Xid is sent to nodes in GridDistributedLockRequest#nearXidVer

   _+Proposed solution+_ : On remote nodes instead of thread id of near transaction GridDistributedLockRequest#threadId
use its xid GridDistributedLockRequest#nearXidVer.
Remove usages of near transaction's thread id on remote nodes.

  was:
Support transaction suspend()\resume() operations for pessimistic transactions. Resume can
be called in another thread.

   _But there is a problem_: Imagine, we started pessimistic transaction in thread T1 and
then perform put operation, which leads to sending GridDistributedLockRequest to another node.
Lock request contains thread id of the transaction. Then we call suspend, resume in another
thread and we also must send messages to other nodes to change thread id. 

It seems complicated task.It’s better to get rid of sending thread id to the nodes.
We can use transaction xid on other nodes instead of thread id. Xid is sent to nodes in GridDistributedLockRequest#nearXidVer

   _Proposed solution_ : On remote nodes instead of thread id of near transaction GridDistributedLockRequest#threadId
use its xid GridDistributedLockRequest#nearXidVer.
Remove usages of near transaction's thread id on remote nodes.


> Context switching for pessimistic transactions
> ----------------------------------------------
>
>                 Key: IGNITE-5714
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5714
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: general
>            Reporter: Alexey Kuznetsov
>            Assignee: Alexey Kuznetsov
>
> Support transaction suspend()\resume() operations for pessimistic transactions. Resume
can be called in another thread.
>    _+But there is a problem+_: Imagine, we started pessimistic transaction in thread
T1 and then perform put operation, which leads to sending GridDistributedLockRequest to another
node. Lock request contains thread id of the transaction. Then we call suspend, resume in
another thread and we also must send messages to other nodes to change thread id. 
> It seems complicated task.It’s better to get rid of sending thread id to the nodes.
> We can use transaction xid on other nodes instead of thread id. Xid is sent to nodes
in GridDistributedLockRequest#nearXidVer
>    _+Proposed solution+_ : On remote nodes instead of thread id of near transaction GridDistributedLockRequest#threadId
use its xid GridDistributedLockRequest#nearXidVer.
> Remove usages of near transaction's thread id on remote nodes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message