Boto3 does not retry DescribeStream call after failure due to LimitExceededException












0















On calling



response = kinesis.describe_stream(StreamName='xxx')


perhaps a bit too frequently, there is a HTTP400 response with LimitExceededException. The unexpected part is that botocore retryhandler thinks this does not require a retry



2018-11-14 13:51:02,771 urllib3.connectionpool [DEBUG] https://kinesis.us-east-1.amazonaws.com:443 "POST / HTTP/1.1" 400 122
2018-11-14 13:51:02,771 botocore.parsers [DEBUG] Response headers: {'x-amzn-RequestId': 'd2203136-53db-60ba-8646-41e0ed56783e', 'x-amz-id-2': 'xxxx', 'connection': 'close', 'Date': 'Wed, 14 Nov 2018 18:51:02 GMT', 'Content-Type': 'application/x-amz-json-1.1', 'Content-Length': '122'}
2018-11-14 13:51:02,771 botocore.parsers [DEBUG] Response body:
b'{"__type":"LimitExceededException","message":"Rate exceeded for stream xxxx under account xxxx"}'
2018-11-14 13:51:02,772 botocore.hooks [DEBUG] Event needs-retry.kinesis.DescribeStream: calling handler <botocore.retryhandler.RetryHandler object at 0x10aa4e940>
2018-11-14 13:51:02,772 botocore.retryhandler [DEBUG] No retry needed.


even though the http status code, service error code and operation match the policy here:
https://github.com/boto/botocore/blob/1.12.4/botocore/data/_retry.json#L174-L181



Retries do occur if I change line 175 to __default__, though that is probably not desired as it would catch other operations. Is my expectation of how retry should work for DescribeStream wrong?










share|improve this question



























    0















    On calling



    response = kinesis.describe_stream(StreamName='xxx')


    perhaps a bit too frequently, there is a HTTP400 response with LimitExceededException. The unexpected part is that botocore retryhandler thinks this does not require a retry



    2018-11-14 13:51:02,771 urllib3.connectionpool [DEBUG] https://kinesis.us-east-1.amazonaws.com:443 "POST / HTTP/1.1" 400 122
    2018-11-14 13:51:02,771 botocore.parsers [DEBUG] Response headers: {'x-amzn-RequestId': 'd2203136-53db-60ba-8646-41e0ed56783e', 'x-amz-id-2': 'xxxx', 'connection': 'close', 'Date': 'Wed, 14 Nov 2018 18:51:02 GMT', 'Content-Type': 'application/x-amz-json-1.1', 'Content-Length': '122'}
    2018-11-14 13:51:02,771 botocore.parsers [DEBUG] Response body:
    b'{"__type":"LimitExceededException","message":"Rate exceeded for stream xxxx under account xxxx"}'
    2018-11-14 13:51:02,772 botocore.hooks [DEBUG] Event needs-retry.kinesis.DescribeStream: calling handler <botocore.retryhandler.RetryHandler object at 0x10aa4e940>
    2018-11-14 13:51:02,772 botocore.retryhandler [DEBUG] No retry needed.


    even though the http status code, service error code and operation match the policy here:
    https://github.com/boto/botocore/blob/1.12.4/botocore/data/_retry.json#L174-L181



    Retries do occur if I change line 175 to __default__, though that is probably not desired as it would catch other operations. Is my expectation of how retry should work for DescribeStream wrong?










    share|improve this question

























      0












      0








      0








      On calling



      response = kinesis.describe_stream(StreamName='xxx')


      perhaps a bit too frequently, there is a HTTP400 response with LimitExceededException. The unexpected part is that botocore retryhandler thinks this does not require a retry



      2018-11-14 13:51:02,771 urllib3.connectionpool [DEBUG] https://kinesis.us-east-1.amazonaws.com:443 "POST / HTTP/1.1" 400 122
      2018-11-14 13:51:02,771 botocore.parsers [DEBUG] Response headers: {'x-amzn-RequestId': 'd2203136-53db-60ba-8646-41e0ed56783e', 'x-amz-id-2': 'xxxx', 'connection': 'close', 'Date': 'Wed, 14 Nov 2018 18:51:02 GMT', 'Content-Type': 'application/x-amz-json-1.1', 'Content-Length': '122'}
      2018-11-14 13:51:02,771 botocore.parsers [DEBUG] Response body:
      b'{"__type":"LimitExceededException","message":"Rate exceeded for stream xxxx under account xxxx"}'
      2018-11-14 13:51:02,772 botocore.hooks [DEBUG] Event needs-retry.kinesis.DescribeStream: calling handler <botocore.retryhandler.RetryHandler object at 0x10aa4e940>
      2018-11-14 13:51:02,772 botocore.retryhandler [DEBUG] No retry needed.


      even though the http status code, service error code and operation match the policy here:
      https://github.com/boto/botocore/blob/1.12.4/botocore/data/_retry.json#L174-L181



      Retries do occur if I change line 175 to __default__, though that is probably not desired as it would catch other operations. Is my expectation of how retry should work for DescribeStream wrong?










      share|improve this question














      On calling



      response = kinesis.describe_stream(StreamName='xxx')


      perhaps a bit too frequently, there is a HTTP400 response with LimitExceededException. The unexpected part is that botocore retryhandler thinks this does not require a retry



      2018-11-14 13:51:02,771 urllib3.connectionpool [DEBUG] https://kinesis.us-east-1.amazonaws.com:443 "POST / HTTP/1.1" 400 122
      2018-11-14 13:51:02,771 botocore.parsers [DEBUG] Response headers: {'x-amzn-RequestId': 'd2203136-53db-60ba-8646-41e0ed56783e', 'x-amz-id-2': 'xxxx', 'connection': 'close', 'Date': 'Wed, 14 Nov 2018 18:51:02 GMT', 'Content-Type': 'application/x-amz-json-1.1', 'Content-Length': '122'}
      2018-11-14 13:51:02,771 botocore.parsers [DEBUG] Response body:
      b'{"__type":"LimitExceededException","message":"Rate exceeded for stream xxxx under account xxxx"}'
      2018-11-14 13:51:02,772 botocore.hooks [DEBUG] Event needs-retry.kinesis.DescribeStream: calling handler <botocore.retryhandler.RetryHandler object at 0x10aa4e940>
      2018-11-14 13:51:02,772 botocore.retryhandler [DEBUG] No retry needed.


      even though the http status code, service error code and operation match the policy here:
      https://github.com/boto/botocore/blob/1.12.4/botocore/data/_retry.json#L174-L181



      Retries do occur if I change line 175 to __default__, though that is probably not desired as it would catch other operations. Is my expectation of how retry should work for DescribeStream wrong?







      boto3 amazon-kinesis botocore






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 15 '18 at 15:36









      RaGeRaGe

      13.5k53774




      13.5k53774
























          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%2f53322876%2fboto3-does-not-retry-describestream-call-after-failure-due-to-limitexceededexcep%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%2f53322876%2fboto3-does-not-retry-describestream-call-after-failure-due-to-limitexceededexcep%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

          Xamarin.iOS Cant Deploy on Iphone

          Glorious Revolution

          Dulmage-Mendelsohn matrix decomposition in Python