Add transaction retry info to production checklist

Fixes #4894.
cockroachdb · Nov 6, 2019 · 004d106 · 004d106
1 parent 033339d
commit 004d106
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/v19.1/recommended-production-settings.md b/v19.1/recommended-production-settings.md
@@ -513,3 +513,7 @@ When running CockroachDB on Kubernetes, making the following minimal customizati
 * Configure CPU and memory [resource requests and limits](kubernetes-performance.html#resource-requests-and-limits).
 
 For more information and additional customization suggestions, see our full detailed guide to [CockroachDB Performance on Kubernetes](kubernetes-performance.html).
+
+## Transaction Retries
+
+When several transactions [are trying to modify the same underlying data concurrently](performance-best-practices-overview.html#understanding-and-avoiding-transaction-contention), all but one will fail. To avoid failures in production, your application should be engineered to handle [transaction retries](transactions.html#transaction-retries) using [client-side retry handling](transactions.html#client-side-intervention).
diff --git a/v19.2/recommended-production-settings.md b/v19.2/recommended-production-settings.md
@@ -514,3 +514,7 @@ When running CockroachDB on Kubernetes, making the following minimal customizati
 * Configure CPU and memory [resource requests and limits](kubernetes-performance.html#resource-requests-and-limits).
 
 For more information and additional customization suggestions, see our full detailed guide to [CockroachDB Performance on Kubernetes](kubernetes-performance.html).
+
+## Transaction Retries
+
+When several transactions [are trying to modify the same underlying data concurrently](performance-best-practices-overview.html#understanding-and-avoiding-transaction-contention), all but one will fail. To avoid failures in production, your application should be engineered to handle [transaction retries](transactions.html#transaction-retries) using [client-side retry handling](transactions.html#client-side-intervention).