Skip to content
This repository has been archived by the owner on Apr 10, 2020. It is now read-only.

413 Request Entity Too Larg - error using AWS Elasticsearch cluster #37

Open
ltagliamonte opened this issue Aug 15, 2016 · 0 comments
Open

Comments

@ltagliamonte
Copy link

ltagliamonte commented Aug 15, 2016

I'm experimenting the following issue using the bulk endpoint of an AWS ElasticSearch Cluster:

2016/08/13 00:31:37 Error uploading to ElasticSearch: Error response from Elasticsearch: 413 Request Entity Too Large Error: request entity too large<br> &nbsp; &nbsp;at readStream (/opt/es_proxy/node_modules/body-parser/node_modules/raw-body/index.js:196:17)<br> &nbsp; &nbsp;at getRawBody (/opt/es_proxy/node_modules/body-parser/node_modules/raw-body/index.js:106:12)<br> &nbsp; &nbsp;at read (/opt/es_proxy/node_modules/body-parser/lib/read.js:76:3)<br> &nbsp; &nbsp;at rawParser (/opt/es_proxy/node_modules/body-parser/lib/types/raw.js:81:5)<br> &nbsp; &nbsp;at Layer.handle [as handle_request] (/opt/es_proxy/node_modules/express/lib/router/layer.js:95:5)<br> &nbsp; &nbsp;at trim_prefix (/opt/es_proxy/node_modules/express/lib/router/index.js:312:13)<br> &nbsp; &nbsp;at /opt/es_proxy/node_modules/express/lib/router/index.js:280:7<br> &nbsp; &nbsp;at Function.process_params (/opt/es_proxy/node_modules/express/lib/router/index.js:330:12)<br> &nbsp; &nbsp;at next (/opt/es_proxy/node_modules/express/lib/router/index.js:271:10)<br> &nbsp; &nbsp;at expressInit (/opt/es_proxy/node_modules/express/lib/middleware/init.js:33:5)

would be nice to add an option to split in chunk the events, so that it is possible to use small AWS ElasticSearch instance type that have 10MB configured as max payload for HTTP requests.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant