Commit 9b7a7f6
fix: narrow retry and reduce max_attempts for connect()
ClusterClient.connect wrapped try_connect in retry_with_backoff with
max_attempts=5 and OperationalError in the retryable set. A non-leader
OperationalError (a real SQL error) was retried 5× find_leader
amplification = 5 × N_nodes RTTs before surfacing.
Since #148 now reclassifies leader-change OperationalErrors into
DqliteConnectionError at connect time, we no longer need
OperationalError in the retry set. Drop it and reduce max_attempts to
3 so a true transport outage surfaces faster.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent c028b0a commit 9b7a7f6
2 files changed
Lines changed: 33 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
124 | 124 | | |
125 | 125 | | |
126 | 126 | | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
| 130 | + | |
| 131 | + | |
127 | 132 | | |
128 | 133 | | |
129 | | - | |
| 134 | + | |
130 | 135 | | |
131 | 136 | | |
132 | 137 | | |
133 | | - | |
134 | 138 | | |
135 | 139 | | |
136 | 140 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
329 | 329 | | |
330 | 330 | | |
331 | 331 | | |
| 332 | + | |
| 333 | + | |
| 334 | + | |
| 335 | + | |
| 336 | + | |
| 337 | + | |
| 338 | + | |
| 339 | + | |
| 340 | + | |
| 341 | + | |
| 342 | + | |
| 343 | + | |
| 344 | + | |
| 345 | + | |
| 346 | + | |
| 347 | + | |
| 348 | + | |
| 349 | + | |
| 350 | + | |
| 351 | + | |
| 352 | + | |
| 353 | + | |
| 354 | + | |
| 355 | + | |
| 356 | + | |
| 357 | + | |
| 358 | + | |
332 | 359 | | |
333 | 360 | | |
334 | 361 | | |
| |||
0 commit comments