From 004d106010ebded4521edbc51971cbe4c7bbea13 Mon Sep 17 00:00:00 2001 From: Rich Loveland Date: Wed, 6 Nov 2019 12:00:45 -0500 Subject: [PATCH] Add transaction retry info to production checklist Fixes #4894. --- v19.1/recommended-production-settings.md | 4 ++++ v19.2/recommended-production-settings.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/v19.1/recommended-production-settings.md b/v19.1/recommended-production-settings.md index 319e6be9779..06236a4e5e5 100644 --- 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 index 255e19192e4..28416740857 100644 --- 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).