Review a Retry for Amplification Risk
Added 2026-11-03
Retries amplify pressure during an outage; check backoff and caps.
Here is code or config that retries. Do: 1) estimate how much request volume is amplified when the dependency is failing; 2) point out missing backoff or jitter; 3) check whether retry counts and timeouts will pile up requests; 4) propose a retry budget per layer; 5) say which operations should never be retried automatically. Do not say "just add retries and it is reliable".
Site original
Chinese original
How to use
重试是可靠性工具，也是故障放大器。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.