Index Level Setting in 5.2.2 after migration from 2.3.1

(Amit) #1


I am migrating to Elastic Search 5.2.2 from 2.3.1, we have successfully migrated index from 2.3.1 to 5.2.2 through Snapshot and Restore.

I have following Index level settings in 2.3.1(Configured in yml), so will migrated indices have this setting at index of 5.2.2

index.query.bool.max_clause_count: 1000000
index.merge.scheduler.max_thread_count: 1
index.max_result_window: 10000

Or do I have to add this setting explicitly on all indices.
If yes, then what is recommended way from ElasticSearch to assign setting to migrated indices.


(Mark Walkom) #2

Some of those settings are pretty excessive, why do you have them?

You will need to set them per index using the APIs.

(Amit) #3

Thanks for Response.

So suppose I have to apply "index.max_result_window: 10000" to indices migrated from 2.3.1 to 5.2.2, so should I Re-Index it?

(system) #4

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