Skip to content
This repository has been archived by the owner on May 24, 2023. It is now read-only.

Allow configuring a timeout for requests #59

Merged
merged 1 commit into from
Apr 8, 2019
Merged

Allow configuring a timeout for requests #59

merged 1 commit into from
Apr 8, 2019

Conversation

csomh
Copy link
Contributor

@csomh csomh commented Apr 5, 2019

  1. Make the timout explicit for gunicorn workers in the Dockerfile.

  2. Extend configuration with a 'REQUEST_TIMEOUT' option, which should be
    considered both for Koji and Quay requests. For the later, the only
    exception is the push operation, as Operator Courier API does not
    have a timeout option yet.

All the above is done, so that the OMPS can be configured in a way,
where requests time out sooner than the workers. This way we hope to
catch some issues currently hidden by the worker timeouts.

Signed-off-by: Hunor Csomortáni csomh@redhat.com

@csomh csomh requested a review from MartinBasti April 5, 2019 15:09
1. Make the timout explicit for gunicorn workers in the Dockerfile.

2. Extend configuration with a 'REQUEST_TIMEOUT' option, which should be
considered both for Koji and Quay requests. For the later, the only
exception is the push operation, as Operator Courier API does not
have a timeout option yet.

All the above is done, so that the OMPS can be configured in a way,
where requests time out sooner than the workers. This way we hope to
catch some issues currently hidden by the worker timeouts.

Signed-off-by: Hunor Csomortáni <csomh@redhat.com>
Copy link
Contributor

@MartinBasti MartinBasti left a comment

Choose a reason for hiding this comment

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

Looks great!

@MartinBasti MartinBasti merged commit ae69353 into release-engineering:master Apr 8, 2019
@MartinBasti
Copy link
Contributor

I forgot about documentation. It should be updated accordingly

@csomh csomh deleted the timeout branch April 15, 2019 08:36
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants