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 a HTTP request with exponential backoff and jitter #264

Open
kanghyojun opened this issue May 9, 2018 · 2 comments
Open

Make a HTTP request with exponential backoff and jitter #264

kanghyojun opened this issue May 9, 2018 · 2 comments
Labels
cmp:transport Component: Transports target:python typ:discuss Type: Discussion typ:enhance Type: Enhancement/new feature

Comments

@kanghyojun
Copy link
Member

Making multiple HTTP requests at once could make a similar effect to DoS attack. So it is helpful to keep service availability that HttpTransport support exponential backoff and jitter when making an HTTP request.

@kanghyojun kanghyojun added dfct:easy Difficulty: Easy typ:enhance Type: Enhancement/new feature cmp:transport Component: Transports target:python dfct:hard Difficulty: Hard and removed dfct:easy Difficulty: Easy dfct:hard Difficulty: Hard labels May 9, 2018
@dahlia dahlia added typ:discuss Type: Discussion and removed dfct:easy Difficulty: Easy labels Jun 9, 2018
@dahlia
Copy link
Member

dahlia commented Jun 9, 2018

A transport implementation is impossible to determine which methods can be retried (i.e., are idempotent) and which methods can't. This should be determined by a programmer who implements the method, and probably annotated as well.

We may need to file a new issue for introducing a method annotation to mark it as idempotent first.

@Kroisse
Copy link
Contributor

Kroisse commented Aug 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cmp:transport Component: Transports target:python typ:discuss Type: Discussion typ:enhance Type: Enhancement/new feature
Projects
None yet
Development

No branches or pull requests

3 participants