You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/10/05 18:46:06 UTC
[jira] [Commented] (GEODE-3679) Server node should forward client
member id to other partition nodes even if it already has a TXState
[ https://issues.apache.org/jira/browse/GEODE-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193429#comment-16193429 ]
ASF subversion and git services commented on GEODE-3679:
--------------------------------------------------------
Commit ca4757aefa4874c973a22dc69c12ccd97eb96138 in geode's branch refs/heads/feature/GEODE-3679 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ca4757a ]
Merge remote-tracking branch 'origin/develop' into feature/GEODE-3679
> Server node should forward client member id to other partition nodes even if it already has a TXState
> -----------------------------------------------------------------------------------------------------
>
> Key: GEODE-3679
> URL: https://issues.apache.org/jira/browse/GEODE-3679
> Project: Geode
> Issue Type: Bug
> Components: transactions
> Affects Versions: 1.1.0, 1.2.0, 1.3.0
> Reporter: Eric Shu
> Assignee: Eric Shu
> Fix For: 1.3.0
>
>
> If the server starts the transaction from client with TXId(clientMember, uniqueId) and bootstrap a TXState as its realDeal, it should still forward the tx originating member to other nodes in a PartitionMessage as long as these msg can not start a new transaction ie FetchKeysMessage.
> Otherwise, the receiving side will construct a transaction with TXId using the server memberId. There could be a case that the server did initiate a real transaction using the same uniqueId. This will cause problem, and other partition node may not process these message as the transaction may be already finished.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)