davebarnes97 commented on a change in pull request #6095:
URL: https://github.com/apache/geode/pull/6095#discussion_r588598937
##########
File path: geode-docs/developing/transactions/design_considerations.html.md.erb
##########
@@ -117,6 +118,21 @@ immediately after the commit.
A transaction disables expiration on any region entries affected
by the transaction.
+## <a id="transactions-nontransactions" class="no-quick-link"></a>Mixing
Transactions with Nontransactional Operations
+
+For best performance, non-transactional operations do not acquire the
exclusive locks used to check
+for conflicts in a transaction. A transaction operating on the same data as a
non-transactional actor
+is unable to detect the conflict caused by a non-transactional operation.
+
+A user application should adopt the policy of always using transactions or no
transactions at all
Review comment:
I've replaced this paragraph with:
If using transactions, an application should adopt the policy of designating
certain regions or sets of entries
exclusively for transactional puts, updates, and deletions, so transactional
entries will not be modified by non-transactional.
operations.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
