# Specifying http.max\_content\_length

**URL:** <https://discuss.elastic.co/t/specifying-http-max-content-length/247804>\
**Category:** Elasticsearch\
**Created:** [September 7, 2020, 7:43pm UTC](https://discuss.elastic.co/t/specifying-http-max-content-length/247804 "2020-09-07T19:43:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcannell](https://avatars.discourse-cdn.com/v4/letter/j/aca169/32.png) [@jcannell](https://discuss.elastic.co/u/jcannell)\
**Post date:** [September 7, 2020, 7:43pm UTC](https://discuss.elastic.co/t/specifying-http-max-content-length/247804/1 "2020-09-07T19:43:16Z")

</div>

Hello,

When specifying `http.max_content_length`, do i need to do this for all nodes in my cluster?

I have a lot of data to index and I'm trying to see if increasing this value might make indexing faster.

I see the question I'm after was asked here: [Increasing http.max\_content\_length](https://discuss.elastic.co/t/increasing-http-max-content-length/188022). Unfortunately in this case it doesn't look like the question was answered.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 7, 2020, 8:56pm UTC](https://discuss.elastic.co/t/specifying-http-max-content-length/247804/2 "2020-09-07T20:56:33Z")

</div>

You do, yes.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 5, 2020, 8:56pm UTC](https://discuss.elastic.co/t/specifying-http-max-content-length/247804/3 "2020-10-05T20:56:35Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
