In order to request a change to search.max_open_scroll_context in Amazon Opensearch, you will need to contact AWS premium support team. Setting the scroll value to higher value is not recommended in general as Scroll API also keeps a track of deleted or updated documents hence increasing the heap memory and disk usage. Hence, the limit of 500 is a safety net defined by the ElasticSearch to avoid any negative impacts on heap memory and disk usage.
That being said, because of managed nature of Amazon Opensearch service this setting can only be changed by opensearch internal team. If you would still like to go ahead and increase this setting, reach out to AWS support team via a support ticket with a specific value you would like it to be increased to.
Note: Please note that this setting will set back to default value (500) when the blue/green deployment is triggered due to a configuration change like version upgrade, changing instance type etc.
In short: Do not change the search.max_open_scroll_context parameter.
We started having problems, after we changed from version 6.8 to 7.7. There it was unlimited.
Vamos implementar uma alternativa para rolar.
Is there a way to find where a private IP/domain points to?Accepted Answerasked 3 years ago
Logging with CloudWatch vs. ElasticSearch/KibanaAccepted Answerasked 5 years ago
using ingest-geoip or Nginx filebeat/metricbeat module on Amazon ElasticSearchAccepted Answerasked a year ago
Bug report: cannot move AWS::Elasticsearch::Domain resource to a new VPCasked 3 months ago
Impact to AWS Elasticsearch on the licensing change of Elasticsearch(elastic.co)Accepted Answerasked a year ago
0 1 How to set permission on Volume mountasked a year ago
Unable to change 'max_buckets' cluster settingasked a year ago
What features of Open Distro is supported by ElasticSearch?Accepted AnswerMODERATORasked 3 years ago
Change ElasticSearch search.max_open_scroll_contextAccepted Answerasked 4 months ago
pagination question on appsync to elasticsearchAccepted Answerasked 3 years ago