What is the correct client reaction to a HTTP 429 when the client is multi-threaded?












3















The HTTP status code 429 tells the client making the request to back off and retry the request after a period specified in the response's Retry-After header.



In a single-threaded client, it is obvious that the thread getting the 429 should wait as told and then retry. But the RFC explicitly states that




this specification does not define how the origin server identifies
the user, nor how it counts requests.




Consequently, in a multi-threaded client, the conservative approach would stop all threads from sending requests until the Retry-After point in time. But:




  • Many threads may already be past the point where they can note the information from the one rejected thread and will send at least one more request.

  • The global synchronization between the threads can be a pain to implement and get right

  • If the setup runs not only several threads but several clients, potentially on different machines, backing off all of them on one 429 becomes non-trivial.


Does anyone have specific data from the field how servers of cloud providers actually handle this? Will they get immediately aggravated if I don't globally hold back all threads. Microsoft's advice is





  1. Wait the number of seconds specified in the Retry-After field.

  2. Retry the request.

  3. If the request fails again with a 429 error code, you are still being throttled. Continue to use the recommended Retry-After delay and retry the request until it succeeds.




It twice says 'the request' not 'any requests' or 'all requests', but this is legal-type interpretation I am not confident about.



To be sure this is not an opinion question, let me phrase it as fact-based as possible:



Are there more detailed specifications for cloud APIs (Microsoft, Google, Facebook, Twitter) then the example above that allow me to make an informed decision whether global back-off is necessary or whether it suffices to back-off with the specific request that got the 429?






multithreading http rate-limiting http-status-code-429







share|improve this question

























  • One hit: docs.microsoft.com/en-us/dynamics365/customer-engagement/… says: "All requests will return these error responses until the volume of API requests falls below the limit." Might be construed as to not needing global back-off, because each requests gets a back-off answer.

    – Harald
    Nov 26 '18 at 8:06
















3















The HTTP status code 429 tells the client making the request to back off and retry the request after a period specified in the response's Retry-After header.



In a single-threaded client, it is obvious that the thread getting the 429 should wait as told and then retry. But the RFC explicitly states that




this specification does not define how the origin server identifies
the user, nor how it counts requests.




Consequently, in a multi-threaded client, the conservative approach would stop all threads from sending requests until the Retry-After point in time. But:




  • Many threads may already be past the point where they can note the information from the one rejected thread and will send at least one more request.

  • The global synchronization between the threads can be a pain to implement and get right

  • If the setup runs not only several threads but several clients, potentially on different machines, backing off all of them on one 429 becomes non-trivial.


Does anyone have specific data from the field how servers of cloud providers actually handle this? Will they get immediately aggravated if I don't globally hold back all threads. Microsoft's advice is





  1. Wait the number of seconds specified in the Retry-After field.

  2. Retry the request.

  3. If the request fails again with a 429 error code, you are still being throttled. Continue to use the recommended Retry-After delay and retry the request until it succeeds.




It twice says 'the request' not 'any requests' or 'all requests', but this is legal-type interpretation I am not confident about.



To be sure this is not an opinion question, let me phrase it as fact-based as possible:



Are there more detailed specifications for cloud APIs (Microsoft, Google, Facebook, Twitter) then the example above that allow me to make an informed decision whether global back-off is necessary or whether it suffices to back-off with the specific request that got the 429?






multithreading http rate-limiting http-status-code-429







share|improve this question

























  • One hit: docs.microsoft.com/en-us/dynamics365/customer-engagement/… says: "All requests will return these error responses until the volume of API requests falls below the limit." Might be construed as to not needing global back-off, because each requests gets a back-off answer.

    – Harald
    Nov 26 '18 at 8:06














3












3








3


1






The HTTP status code 429 tells the client making the request to back off and retry the request after a period specified in the response's Retry-After header.



In a single-threaded client, it is obvious that the thread getting the 429 should wait as told and then retry. But the RFC explicitly states that




this specification does not define how the origin server identifies
the user, nor how it counts requests.




Consequently, in a multi-threaded client, the conservative approach would stop all threads from sending requests until the Retry-After point in time. But:




  • Many threads may already be past the point where they can note the information from the one rejected thread and will send at least one more request.

  • The global synchronization between the threads can be a pain to implement and get right

  • If the setup runs not only several threads but several clients, potentially on different machines, backing off all of them on one 429 becomes non-trivial.


Does anyone have specific data from the field how servers of cloud providers actually handle this? Will they get immediately aggravated if I don't globally hold back all threads. Microsoft's advice is





  1. Wait the number of seconds specified in the Retry-After field.

  2. Retry the request.

  3. If the request fails again with a 429 error code, you are still being throttled. Continue to use the recommended Retry-After delay and retry the request until it succeeds.




It twice says 'the request' not 'any requests' or 'all requests', but this is legal-type interpretation I am not confident about.



To be sure this is not an opinion question, let me phrase it as fact-based as possible:



Are there more detailed specifications for cloud APIs (Microsoft, Google, Facebook, Twitter) then the example above that allow me to make an informed decision whether global back-off is necessary or whether it suffices to back-off with the specific request that got the 429?






multithreading http rate-limiting http-status-code-429







share|improve this question
















The HTTP status code 429 tells the client making the request to back off and retry the request after a period specified in the response's Retry-After header.



In a single-threaded client, it is obvious that the thread getting the 429 should wait as told and then retry. But the RFC explicitly states that




this specification does not define how the origin server identifies
the user, nor how it counts requests.




Consequently, in a multi-threaded client, the conservative approach would stop all threads from sending requests until the Retry-After point in time. But:




  • Many threads may already be past the point where they can note the information from the one rejected thread and will send at least one more request.

  • The global synchronization between the threads can be a pain to implement and get right

  • If the setup runs not only several threads but several clients, potentially on different machines, backing off all of them on one 429 becomes non-trivial.


Does anyone have specific data from the field how servers of cloud providers actually handle this? Will they get immediately aggravated if I don't globally hold back all threads. Microsoft's advice is





  1. Wait the number of seconds specified in the Retry-After field.

  2. Retry the request.

  3. If the request fails again with a 429 error code, you are still being throttled. Continue to use the recommended Retry-After delay and retry the request until it succeeds.




It twice says 'the request' not 'any requests' or 'all requests', but this is legal-type interpretation I am not confident about.



To be sure this is not an opinion question, let me phrase it as fact-based as possible:



Are there more detailed specifications for cloud APIs (Microsoft, Google, Facebook, Twitter) then the example above that allow me to make an informed decision whether global back-off is necessary or whether it suffices to back-off with the specific request that got the 429?






multithreading http rate-limiting http-status-code-429




multithreading http rate-limiting http-status-code-429






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 26 '18 at 8:00







Harald

















asked Nov 24 '18 at 10:59









HaraldHarald

2,1811637




2,1811637













  • One hit: docs.microsoft.com/en-us/dynamics365/customer-engagement/… says: "All requests will return these error responses until the volume of API requests falls below the limit." Might be construed as to not needing global back-off, because each requests gets a back-off answer.

    – Harald
    Nov 26 '18 at 8:06



















  • One hit: docs.microsoft.com/en-us/dynamics365/customer-engagement/… says: "All requests will return these error responses until the volume of API requests falls below the limit." Might be construed as to not needing global back-off, because each requests gets a back-off answer.

    – Harald
    Nov 26 '18 at 8:06

















One hit: docs.microsoft.com/en-us/dynamics365/customer-engagement/… says: "All requests will return these error responses until the volume of API requests falls below the limit." Might be construed as to not needing global back-off, because each requests gets a back-off answer.

– Harald
Nov 26 '18 at 8:06





One hit: docs.microsoft.com/en-us/dynamics365/customer-engagement/… says: "All requests will return these error responses until the volume of API requests falls below the limit." Might be construed as to not needing global back-off, because each requests gets a back-off answer.

– Harald
Nov 26 '18 at 8:06












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53457432%2fwhat-is-the-correct-client-reaction-to-a-http-429-when-the-client-is-multi-threa%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53457432%2fwhat-is-the-correct-client-reaction-to-a-http-429-when-the-client-is-multi-threa%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Contact image not getting when fetch all contact list from iPhone by CNContact

Image
up vote 0 down vote favorite I know this question already asked but not getting solution. From this code I will get all the information from the contact but image not found when open vcf files on mac os, also not getting when share this file. I use this stackoverflow link here but It's not help full. var contacts = [CNContact]() let keys = [CNContactVCardSerialization.descriptorForRequiredKeys() ] as [Any] let request = CNContactFetchRequest(keysToFetch: keys as! [CNKeyDescriptor]) do { try self.contactStore.enumerateContacts(with: request) { (contact, stop) in // Array containing all unified contacts from everywhere contacts.append(contact) } } catch { print("unable to fetch contacts") } do { let data = try
Read more

count number of partitions of a set with n elements into k subsets

Image
up vote 6 down vote favorite 1 This program is for count number of partitions of a set with n elements into k subsets I am confusing here return k*countP(n-1, k) + countP(n-1, k-1); can some one explain what is happening here? why we are multiplying with k? NOTE->I know this is not the best way to calculate number of partitions that would be DP // A C++ program to count number of partitions // of a set with n elements into k subsets #include<iostream> using namespace std; // Returns count of different partitions of n // elements in k subsets int countP(int n, int k) { // Base cases if (n == 0 || k == 0 || k > n) return 0; if (k == 1 || k == n) return 1; // S(n+1, k) = k*S(n, k) + S(n, k-1) return k*countP(n-1, k) + countP(n-1, k-1); } // Driver program int ma
Read more

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Image
0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{
Read more