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

Retry 400 Bad errors #605

Closed
bbangert opened this issue Aug 17, 2016 · 0 comments
Closed

Retry 400 Bad errors #605

bbangert opened this issue Aug 17, 2016 · 0 comments
Assignees
Labels

Comments

@bbangert
Copy link
Member

bbangert commented Aug 17, 2016

For 'reasons', we sometimes get a flakey 400 Bad Request for a security token. These requests should be retried or return a 503, and ping a metric so we know they still happen. Logging to Sentry isn't needed though.

JSONResponseError: JSONResponseError: 400 Bad Request
{u'message': u'The security token included in the request is invalid.', u'__type': u'com.amazon.coral.service#UnrecognizedClientException'}
(6 additional frame(s) were not displayed)
...
  File "boto/dynamodb2/table.py", line 913, in delete_item
    conditional_operator=conditional_operator)
  File "boto/dynamodb2/layer1.py", line 925, in delete_item
    body=json.dumps(params))
  File "boto/dynamodb2/layer1.py", line 2842, in make_request
    retry_handler=self._retry_handler)
  File "boto/connection.py", line 954, in _mexe
    status = retry_handler(response, i, next_sleep)
  File "boto/dynamodb2/layer1.py", line 2885, in _retry_handler
    data)
@bbangert bbangert added this to the PUSHSVC-0: quality milestone Aug 17, 2016
@bbangert bbangert self-assigned this Aug 18, 2016
jrconlin added a commit that referenced this issue Aug 18, 2016
jrconlin added a commit that referenced this issue Aug 18, 2016
@bbangert bbangert assigned jrconlin and bbangert and unassigned bbangert and jrconlin Aug 19, 2016
jrconlin added a commit that referenced this issue Aug 19, 2016
jrconlin added a commit that referenced this issue Aug 19, 2016
jrconlin added a commit that referenced this issue Aug 19, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants