[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=16193937#comment-16193937 ] ASF subversion and git services commented on GEODE-3679: Commit 9690c09fc479c880824e0f998f7d3176fef03979 in geode's branch refs/heads/develop from [~eshu] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9690c09 ] GEODE-3679 Forward client member id to other peers in transaction message. * Do not forward size request of a bucket region to transaction hosting node. * Move the method from LocalRegion to DistributedRegion. * Make region in TXRegionStub strong type to avoid some casting in the code. > 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)
[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=16193934#comment-16193934 ] ASF subversion and git services commented on GEODE-3679: Commit c34132f3f1cf99163ef4b0dcb1055fd0a73525ed in geode's branch refs/heads/feature/GEODE-3679 from [~eshu] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c34132f ] GEODE-3679 Forward client member id to other peers in transaction message. * Do not forward size request of a bucket region to transaction hosting node. * Move the method from LocalRegion to DistributedRegion. * Make region in TXRegionStub strong type to avoid some casting in the code. > 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)
[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=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)
[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=16185942#comment-16185942 ] Eric Shu commented on GEODE-3679: - The fix reveals another issue in region.size() call in transaction. Will provide a fix of this as well. When a server starts transaction with PeerTXStateStub, (TXState resides on another server), it will send partitioned region.entryCount to the server hosting the tx. The hosting server gets size info of all the buckets from itself and all other nodes. Currently when the first server receive the request for size, it will go through the code path and sending the request back to the hosting server to get the size. This leads to the actual size information from the buckets it hosts to be lost. > 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 > > 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)
