Commit f20c96d
waterWang
fix: make perAttemptRecvTimeout actually apply to retry attempts
The perAttemptRecvTimeout field in RetryPolicy has been configurable since
PR #8301 but was never actually applied to individual retry attempts.
The DeadlineEntry in RetriableStream.setDeadline() simply passed through
the original deadline without considering the per-attempt timeout.
Fix: When perAttemptRecvTimeoutNanos is set in the retry policy, apply
the minimum of the original deadline and the per-attempt deadline to
each substream. This ensures that each retry attempt is bounded by the
per-attempt timeout, relative to when the attempt starts.
Fixes #12919
[fj4WqyCCw3C5ShR1RfB7MoBPTpkRrBFYP1uT35g3MvT]1 parent 3b3002c commit f20c96d
1 file changed
Lines changed: 7 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
754 | 754 | | |
755 | 755 | | |
756 | 756 | | |
757 | | - | |
| 757 | + | |
| 758 | + | |
| 759 | + | |
| 760 | + | |
| 761 | + | |
| 762 | + | |
| 763 | + | |
758 | 764 | | |
759 | 765 | | |
760 | 766 | | |
| |||
0 commit comments