[
https://issues.apache.org/jira/browse/GEODE-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626103#comment-14626103
]
ASF subversion and git services commented on GEODE-16:
------------------------------------------------------
Commit d6f9fde22b4398c5d992738e56dcc696a1082312 in incubator-geode's branch
refs/heads/feature/GEODE-16 from Vivek Bhaskar
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=d6f9fde ]
GEODE-16 Fixing a failure of
AnalyzeSerializablesJUnitTest.testDataSerializables that got introduced in my
last checkin (1f6462876fe4056e820db74cfc7db8af70f7a01f).wq
> Provide distributed transactions in Geode
> -----------------------------------------
>
> Key: GEODE-16
> URL: https://issues.apache.org/jira/browse/GEODE-16
> Project: Geode
> Issue Type: New Feature
> Components: core
> Reporter: Shirish Deshmukh
> Assignee: Shirish Deshmukh
> Attachments: DistributedTransactionDesign.pdf
>
>
> This is a feature that has been under design for GemFire but was not part of
> the initial drop of code for geode.
> Currently in Geode a transactional operation can only be applied on colocated
> data i.e. all the key-value pairs affected in a transaction should be on
> single VM.
> We should allow operations on multiple VMs simultaneously in a single
> transaction, which would eliminate current restrictions.
> Some of the implicit requirements for this feature are:
> Provide distributed transaction feature that would also be scalable
> Continue to support existing transaction functionalities (transactions on
> colocated data)
> Do not affect performance of existing features
> Support backward compatibility and rolling upgrade (with immediate previous
> Geode release)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
