Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make 404 an optionally recoverable error when calling rest api endpoint #2072

Closed
benedeki opened this issue May 24, 2022 · 1 comment · Fixed by #2087
Closed

Make 404 an optionally recoverable error when calling rest api endpoint #2072

benedeki opened this issue May 24, 2022 · 1 comment · Fixed by #2087
Assignees
Labels
Conformance Conformance Job affected feature New feature priority: medium Important but not urgent Standardization Standardization Job affected under discussion Requires consideration before a decision is made whether/how to implement

Comments

@benedeki
Copy link
Collaborator

Background

When call from Spark Job to Menas REST API fails, if the error is considered recoverable another of the configured servers is tried.

Feature

404 is not considered recoverable. Make it configurable that 404 can be considered recoverable to try a different server.

Bonus [Optional]

Maybe it could be done generally, that a list of error status codes can be configured, that will be considered recoverable.

@benedeki benedeki added Conformance Conformance Job affected feature New feature priority: medium Important but not urgent Standardization Standardization Job affected under discussion Requires consideration before a decision is made whether/how to implement labels May 24, 2022
lsulak added a commit that referenced this issue Jun 16, 2022
… changing DaoException not to be retryable by default
lsulak added a commit that referenced this issue Jun 16, 2022
lsulak added a commit that referenced this issue Jun 16, 2022
…without it, we compare the content of the sets in our tests)
lsulak added a commit that referenced this issue Jun 17, 2022
…tom exception that's being used for the DAO module and removing var canBeRecovered
lsulak added a commit that referenced this issue Jun 17, 2022
lsulak added a commit that referenced this issue Jun 27, 2022
lsulak added a commit that referenced this issue Jun 27, 2022
lsulak added a commit that referenced this issue Jun 27, 2022
lsulak added a commit that referenced this issue Jun 27, 2022
lsulak added a commit that referenced this issue Jun 28, 2022
lsulak added a commit that referenced this issue Jul 18, 2022
…ups: Not Retryable, Retryable, and Optionally Retryable errors; this was basically implemented already, but not clearly expressed
lsulak added a commit that referenced this issue Jul 18, 2022
lsulak added a commit that referenced this issue Jul 18, 2022
lsulak added a commit that referenced this issue Jul 18, 2022
…conformance's config (as recently is implemented in HyperConformanceAttributes)
lsulak added a commit that referenced this issue Jul 18, 2022
lsulak added a commit that referenced this issue Jul 18, 2022
lsulak added a commit that referenced this issue Jul 18, 2022
@benedeki benedeki linked a pull request Jul 19, 2022 that will close this issue
lsulak added a commit that referenced this issue Jul 25, 2022
lsulak added a commit that referenced this issue Aug 24, 2022
lsulak added a commit that referenced this issue Aug 24, 2022
…other problems (e.g 404) than just authentization
lsulak added a commit that referenced this issue Aug 24, 2022
lsulak added a commit that referenced this issue Aug 24, 2022
lsulak added a commit that referenced this issue Aug 25, 2022
…re precise in terms of its responsibilities
lsulak added a commit that referenced this issue Aug 25, 2022
lsulak added a commit that referenced this issue Aug 25, 2022
lsulak added a commit that referenced this issue Aug 25, 2022
lsulak added a commit that referenced this issue Aug 26, 2022
lsulak added a commit that referenced this issue Aug 26, 2022
lsulak added a commit that referenced this issue Aug 26, 2022
lsulak added a commit that referenced this issue Aug 28, 2022
@lsulak
Copy link
Collaborator

lsulak commented Sep 2, 2022

Release notes

A user can specify a list of HTTP error status codes that are allowed to be retried when a REST API call yields such an HTTP error. Currently supported HTTP error status codes: 401, 403, and 404.

lsulak added a commit that referenced this issue Sep 2, 2022
* #2072 adding retryableException parameter into CrossHostApiCaller, AuthClient, and reference.conf config file
* #2072 enhancing config loading functionality providing support for the retryableException parameter
* #2072 refactoring DAOException module
* #2072 unit tests confirming the correct functionality of this feature



Co-authored-by: David Benedeki <14905969+benedeki@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Conformance Conformance Job affected feature New feature priority: medium Important but not urgent Standardization Standardization Job affected under discussion Requires consideration before a decision is made whether/how to implement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants