[
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.
Discussion on dev list can be found
[here|http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-5714-Design-proposal-of-suspend-resume-for-pessimistic-tx-tt27410.html]
> Implementation of suspend/resume 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
> Priority: Major
> Fix For: 2.6
>
>
> 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
(v7.6.3#76005)
