Reverting retry behavior on 429s/503s to how it worked in 2.9.3 #349
Conversation
benc-db
requested review from
arikfr,
yunbodeng-db and
andrefurlan-db
as code owners
|
Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase ( |
1 similar comment
|
Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase ( |
benc-db
force-pushed
the
retry_revisited
branch
from
82787c0
to
fc21c2e
Compare
benc-db
requested review from
rcypher-databricks and
jackyhu-db
as code owners
|
Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase ( |
linted rebased Signed-off-by: Ben Cassell <ben.cassell@databricks.com> fixing failing tests
benc-db
force-pushed
the
retry_revisited
branch
from
64f7cbc
to
09c1c0f
Compare
In version 3 we started accepting Retry-After exactly on 429s/503s, as opposed to using it as a floor for exponential backoff. After consulting with SQL Gateway team, it is best to bring that behavior back. Apologies for the formatting differences, this was automatically performed by VS Code.