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

report, lock.ops, lock.query: add retry mechanism to paddles requests #1656

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

amathuria
Copy link
Contributor

We need requests to paddles to retry multiple times in case of 500
errors from the DB server. This change adds a retry mechanism to the
paddles requests that previously did not have one.

Fixes: https://tracker.ceph.com/issues/50921
Signed-off-by: Aishwarya Mathuria [email protected]

@kshtsk
Copy link
Contributor

kshtsk commented Jun 25, 2021

  1. Do we know why error 500 happens? Maybe fix it instead?
  2. The code with the whiles looks clumsy and hard to maintain. If we really want all paddles requests to be retried several time (which already sound weird and buggy design) maybe we can have a wrapper for paddles request, like isolated in a separate module?

We need requests to paddles to retry multiple times in case of 500
errors from the DB server. This change adds a retry mechanism to the
paddles requests that previously did not have one.

Fixes: https://tracker.ceph.com/issues/50921
Signed-off-by: Aishwarya Mathuria <[email protected]>
@djgalloway
Copy link

1. Do we know why error 500 happens?

ceph/paddles#93

elif reimage and machine_type in reimage_types:
return reimage_machines(ctx, machines, machine_type)
return machines
elif response.status_code == 503:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do I understand correctly that it is trying to retry on any error, not only 500?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that is correct.

@djgalloway djgalloway changed the base branch from master to main June 1, 2022 17:03
@kshtsk
Copy link
Contributor

kshtsk commented Jul 2, 2024

there are conflicts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants