413 - Request Entity Too Large

Question

We are using Azure Search, and we are indexing documents in batches of 1000, as recommended.

But today we got the error "413 - Request Entity Too Large" during indexing.

Our documents are quite small.

What exactly is the limitation we ran into?  How do we handle it the best way?

Regards,
Vilhelm Heiberg, ExorLive AS

---

Vilhelm Heiberg, ExorLive AS

Answer 1

Hi Vilhelm,

The limit is approximately 16 MB per request for every request in the API. How small are your documents? It is unusual to run into this limitation with small documents.

If you like you can e-mail me at bruce DOT johnston AT microsoft and we can investigate further. I'll need your search service name, Azure geo-location (e.g. -- East US, West Europe, etc.), and the date & time of the requests that failed with 413.

Thanks,

-Bruce

Answer 2

Thank you . That makes sense. It turned out my documents were larger than I first thought.

---

Vilhelm Heiberg, ExorLive AS

Answer 3

Very interesting, so if I'm using Postman to POST a large JSON file ( around 28MG) then it can't be done right?

I got a 413 request entity too large

Time: 1486ms

Size: 273B

Answer 4

Also, how do I create an index for this type of nested JSON were "coord" is nested object????

        {
            "id": 519188,
            "city": "Novinki",
            "country": "RU",
            "coord": {
                "lon": 37.666668,
                "lat": 55.683334
            }
        }

Answer 5

Found that this can be a Edm.ComplexType

thanks. Great documentation Microsoft!