New circuit breaker on context.template.max_compilations_rate trips for ingest pipelines

[slylock]

Describe the bug

This circuit breaker did not exist in version 2.7. When I upgraded to 2.11, the circuit breaker started tripping for ingest pipelines that use Mustache. Unfortunately I'm unable to increase the 75/5m limit because I'm using AWS-hosted OpenSearch. Should this setting apply to ingest pipelines? If so, the limit effectively makes it impossible to use Mustache in an ingest pipeline.

Related component

Indexing

To Reproduce

Any use of Mustache in an ingest pipeline, with a indexing job of more than 75 docs, will trip the breaker. For example: { "processors": [ {"set": {"field": "_source.surl" , "value": "{{_source.murl}}"}}, {"set": {"field": "_source.llevel" , "value": "{{_source.schoollevel}}"}}

Expected behavior

Perhaps ingest pipeline context needs a separate setting with a much higher default limit.

Additional Details

Plugins Please list all plugins currently enabled.

Screenshots If applicable, add screenshots to help explain your problem.

Host/Environment (please complete the following information):

• OS: [e.g. iOS]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[peternied]

[Triage - attendees 1 2 3 4 5 6 7 8] @slylock Thanks for creating this issue

[peternied]

@slylock You might also want to submit a support request with the AWS service as the problem could be on their end

[slylock]

I don't think this is a real bug. After I deleted and re-PUT the offending pipeline, I'm not getting the error anymore. So it seems like an anomaly of the AWS upgrade process only.

[dhwanilpatel]

[Indexing Triage 09/16]

Thanks for the confirmation @slylock that this is not bug. Closing the issue.