Dave Barnes created GEODE-8953:
----------------------------------
Summary: User Guide - re-introduce transaction details regarding
non-transactional changes
Key: GEODE-8953
URL: https://issues.apache.org/jira/browse/GEODE-8953
Project: Geode
Issue Type: Bug
Components: docs
Reporter: Dave Barnes
Community member @alberto.gomez requests that we re-introduce some verbiage
that was deleted in the fix for "GEODE-5509: Rewrite the docs on transaction."
The passage to re-instate is:
"If other, non-transactional sources update the keys the transaction is
modifying, the changes may intermingle with this transaction’s changes. The
other sources can include distributions from remote members, loading
activities, and other direct cache modification calls from the same member.
When this happens, after your commit finishes, the cache state may not be what
you expected."
[~eshu]Â concurs, providing the background explanation:
To achieve best performance, non-transactional operations do not acquire DLock
used to check conflicts in a transaction. So transaction will not be able to
detect the conflict caused by a non transactional operation. It is expected
that user application always uses transaction or no transaction at all, unless
user knows that certain regions or set of entries will not be modified by
operations outside of a transaction.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
