Hey All, Presently we treat 503 status code in spec here <http:///> as if the request was not tried at all. While doing 1.9.2 it was brought up that this exception might not be true and some of the very common services like Istio and Envoy were brought up as examples.
As a result I wanted to formally bring up disabling retries on 503 on updateTable and treating that as CommitStateUnknown similar to what we do for 500, 502, 504. The rationale for this being 503 doesn't necessarily mean the request was not tried at all and systems like ENVOY can return 503 in the middle of processing. Adding detailed analysis of my colleague Dennis here : https://lists.apache.org/thread/h8xowcntomh7r5woz24cv27v3o8r9wgd It seemed like most people participating in the thread above agreed, starting this thread to see if there are objections to it in a wider forum. Meanwhile, I have filed a PR for the same [1] https://github.com/apache/iceberg/pull/13619 Please let us know your thoughts and provide your feedback ! Best, Prashant Singh
