Add transaction retry info to production checklist #5797
Conversation
|
This change is |
There was a problem hiding this comment.
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @jseldess and @rmloveland)
v19.1/recommended-production-settings.md, line 519 at r1 (raw file):
## 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).
Is "all but one will fail" too extreme? Don't we retry automatically in a lot of cases but want client-side retry logic for the cases where we don't?
rmloveland
force-pushed
the
20191106-txn-retries-production-checklist
branch
from
25598b1 to
2e72b07
Compare
There was a problem hiding this comment.
Reviewable status:
v19.1/recommended-production-settings.md, line 519 at r1 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
Is "all but one will fail" too extreme? Don't we retry automatically in a lot of cases but want client-side retry logic for the cases where we don't?
You're right! I got some tunnel vision trying to re-use the language in the original issue that was filed.
Updated to be more nuanced and, I think, correct this time. PTAL.
|
@jseldess are you OK with these edits? |
|
Yes, LGTM now, Rich. Thank you! |
|
Thanks Jesse! |
Fixes #3266.