Skip to content

[database] refactor retry logic only for errors worth retrying #2391

@KarlG-nbis

Description

@KarlG-nbis

Please describe the feature

As a repository operator, I want database queries to be retried when a retry could be expected to succeed so that we dont react to the error when not neccesary.

Acceptance criteria

  • Tests verifying the changes are added

Additional context

We should mainly check for connection errors.
We should have retry logic with a backoff policy with configurable values.
Retry logic should be context-aware such that if client cancells request, etc the retry logic should stop.

Estimation of size

small/medium/big

Estimation of priority

low/medium/high

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions