{"_id":"568ade3697d8960d0012ab4c","__v":4,"version":{"_id":"5633ec007e9e880d00af1a56","project":"5633ebff7e9e880d00af1a53","__v":15,"createdAt":"2015-10-30T22:15:28.105Z","releaseDate":"2015-10-30T22:15:28.105Z","categories":["5633ec007e9e880d00af1a57","5633f072737ea01700ea329d","5637a37d0704070d00f06cf4","5637cf4e7ca5de0d00286aeb","564503082c74cf1900da48b4","564503cb7f1fff210078e70a","567af26cb56bac0d0019d87d","567afeb8802b2b17005ddea0","567aff47802b2b17005ddea1","567b0005802b2b17005ddea3","568adfffcbd4ca0d00aebf7e","56ba80078cf7c9210009673e","574d127f6f075519007da3d0","574fde60aef76a0e00840927","57a22ba6cd51b22d00f623a0"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"parentDoc":null,"user":"5633eb67737ea01700ea328b","category":{"_id":"564503082c74cf1900da48b4","__v":13,"project":"5633ebff7e9e880d00af1a53","version":"5633ec007e9e880d00af1a56","pages":["564503117f1fff210078e707","564504a8b360ea0d00914852","564504aeb360ea0d00914854","564504b32229d7170010926d","564504bf6b0ca50d00f6bd6b","564504c62c74cf1900da48b9","564504ccd608df0d00d26a21","564504d72c74cf1900da48bb","564504df7f1fff210078e70b","564504e66b0ca50d00f6bd6e","564504ebb360ea0d00914858","568ade3697d8960d0012ab4c","568b2c687a42220d004982bf"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-11-12T21:22:16.300Z","from_sync":false,"order":6,"slug":"troubleshooting-common-errors","title":"Troubleshooting"},"project":"5633ebff7e9e880d00af1a53","updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-01-04T21:03:50.037Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"HTTP 429\"\n}\n[/block]\nAn app that exceeds both its concurrency limits and queue limits will see 429 error responses on new requests, until the queue begins to drain. If your app is experiencing 429 requests, you may need to perform additional batching of your updates (e.g. queueing and bulk updating) or searches (e.g. with multi-search API). \n\nIn most cases, 429 errors can be solved by upgrading your plan to a plan with higher connection limits; new connection limits are applied immediately.\n\nUnusually expensive requests, or other unusual latency and performance degradation within Elasticsearch, can also cause unexpected queueing and result in 429 errors. We have some suggestions for [optimizing your requests](doc:connection-management) that can help point your in the right direction. And you can always [contact us](mailto:support:::at:::bonsai.io) for additional help identifying and troubleshooting the source of persistent unexpected 429 errors.","excerpt":"","slug":"troubleshooting-http-error-codes","type":"basic","title":"HTTP 429: Too Many Concurrent Connections"}

HTTP 429: Too Many Concurrent Connections


[block:api-header] { "type": "basic", "title": "HTTP 429" } [/block] An app that exceeds both its concurrency limits and queue limits will see 429 error responses on new requests, until the queue begins to drain. If your app is experiencing 429 requests, you may need to perform additional batching of your updates (e.g. queueing and bulk updating) or searches (e.g. with multi-search API). In most cases, 429 errors can be solved by upgrading your plan to a plan with higher connection limits; new connection limits are applied immediately. Unusually expensive requests, or other unusual latency and performance degradation within Elasticsearch, can also cause unexpected queueing and result in 429 errors. We have some suggestions for [optimizing your requests](doc:connection-management) that can help point your in the right direction. And you can always [contact us](mailto:support@bonsai.io) for additional help identifying and troubleshooting the source of persistent unexpected 429 errors.