Skip to content
This repository has been archived by the owner on Apr 21, 2022. It is now read-only.

Delayed-request update strategy #11

Open
blackandred opened this issue Jun 6, 2020 · 1 comment
Open

Delayed-request update strategy #11

blackandred opened this issue Jun 6, 2020 · 1 comment
Labels
enhancement New feature or request
Milestone
Harbor 2.3

Comments

@blackandred
Copy link
Contributor

blackandred commented Jun 6, 2020 •
edited

Idea:
"delayed-request" strategy can be implemented if possible (delay current requests on gateway - extend timeout until the service is not replaced)

Notice: This is an investigation + implementation task. If the investigation would result in - "cannot do" then this feature should be cancelled.

Effect:
Users would not get 500 error or other weird errors, they would need to wait a few seconds more for page to load
@blackandred blackandred added the enhancement New feature or request label Jun 6, 2020
@blackandred blackandred added this to the Harbor 2.1 milestone Jun 6, 2020
@blackandred
Copy link
Contributor Author

https://stackoverflow.com/questions/45901243/add-delay-between-retries-when-origin-is-down-nginx-502

@blackandred blackandred modified the milestones: Harbor 2.1, Harbor 2.3 Nov 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
Harbor 2.3
Development

No branches or pull requests
1 participant
@blackandred