Unable to set mustache.max_output_size_bytes in elasticsearch.yml version 7.17.25

Hi,

We have recently upgraded to 7.17.25 and trying to set the below configuration in elasticsearch.yml as recommended in the release notes

mustache.max_output_size_bytes: 10485760

however we see that configuration is not picked up by elatsicsearch at startup and throwing the Exception as below

java.lang.IllegalArgumentException: failed to parse setting [mustache.max_output_size_bytes] with value [10485760] as a size in bytes: unit is missing or unrecognized

Try looks like the setting needs units

mustache.max_output_size_bytes: 1mb

So 2mb would be

mustache.max_output_size_bytes: 2mb

See

Thanks Stephen.

I have set the value as recommended but now i am seeing a different exception at the start up. Look like the setting itself is not recognized. Am i missing anything?

org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [mustache.max_output_size_bytes] please check that any required plugins are installed, or check the breaking changes documentation for removed settings

1 Like

Hmmm I am seeing the same things... I will try to check internally... Its US / UK holiday... so you may not get an answer right away

I understand. Will wait for your response. I tried this configuration in both 7.17.25 and 7.17.26. Both versions are giving the same exception.

TO be clear the new default is 1mb do you need more than that... that is quite a long script...

Unfortunately, yes, we need more than 1mb until we find a way to optimize.
These are existing scripts which were running fine on 7.17.11 until we upgrade to 7.17.25 last week.

There is a bug... thee setting was not properly "registered" so it can not be set at this time...

There is going to be a PR opened when it does I will paste it here for you to track.

Here is the PR

Thanks Stephen. I know it is a bit early to ask, do you have any timeline on when this will be fixed?

No and I do not control that, and Elastic does not announce release dates ahead of time.

I would suggest to follow the PR it is already in the process of being merged....

It is tagged for

Keep an eye out for the 7.17.27 release...