Elastic cloud request entity max length

Hello,

i have an elastic cloud cluster and im facing a request entity payload that seems to be too large

the error received on the console is :

{
  "statusCode": 413,
  "error": "Request Entity Too Large",
  "message": "Payload content length greater than maximum allowed: 1048576"
}

So the limit seems to be around 1Mbits or 1Mbytes , the unit is not given here by the way

so i checked the cluster maximum limits with a request

GET /_clusters/settings?include_defaults

i've seen many topics complaining about http.max_content_length param so i've checked this one it says :

"max_content_length": "100mb",

as far as i understand this is the maximum size of an uploaded document in mbits wich gives around 12Mbytes

but this number has nothing to do with the previous one sent by the error which is only 1M not 100M

plus it seems that for cloud instance it is not possible to increase the http.max_content_length anyway

my question is the following

i'm reaching the limit of the request payload itself when querying an index, not the limit when indexing something

  1. but where is this limit ?
  2. what is the parameter name ?
  3. is it possible to increase it for cloud instance customers ?

as the numbers are totally different my guess is that the interesting parameter has nothing to do with http.max_content_length because 100mbit would have done the job.

My payload size copy pasted to a file on my computer is 1.1MBytes so around 9.2Mbits so i should not have reached the limit anyway

thanks for any help on this

Thanks for reaching out, @dealomuss.

It seems from this older forum post you may be able to make adjustments to this, but I'm not sure if this will work on cloud. This guide may also be helpful too.

1 Like

hello jess,

thank you so much for taking the time to answer and so quickly

the first link is dealing about index document size wich did not help

BUT the second one put me on the right track because of the exact same value for the limitation

so to the limitation concernning the request entity payload ( wich is different from the size of document to be indexed ) is indeed a Kibana limitation not Elastic

i've upgraded the value in elastic cloud parameter it worked perfectly !

i had to deal with max index term count after that but it was just an index setting to adjust

if anyone else is facing this problem and dealing with huge request payloads here are the two things to move

in your cloud instance kibana's user setting yml

server.maxPayload: 104857600

on your index for increasing term counts

PUT /myindexname/_settings
{
    "index" : {
        "max_terms_count" :  1000000  
     }
}

thank you for your help !

1 Like

Thanks so much for this detailed follow up, @dealomuss.