Optimize Elasticsearch index -
due low disk space , large amount of deleted documents inside 1 of index, need optimize command (elasticsearch 1.7)
right now, index has following stats:
shards: 15 * 1 | docs: 23,165,760 | size: 1.25tb
- will optimize api block indexing/query operation untill optimization done?
- will optimize api affects operations on other indexes?
- is possible have approximate time know how long take?
sorry bad english :)
and let me know if need further stats
will optimize api block indexing/query operation untill optimization done?
no, can run in parallel, indexing process affect optimization. new segments created, subject optimization well...
will optimize api affects operations on other indexes?
not directly, indirectly using additional cpu, memory , disk.
is possible have approximate time know how long take?
nop :-), maybe testing upfront , extrapolating number of documents/segments.
be careful optimization require additional disk space. if optimize low number of segments, optimization process try optimize set of large segments in end means need additional (largesegment1_size + largesegment2_size + ....) disk space. old segments deleted when resulting merged segment complete.
also, @ only_expunge_deletes option alternative.
another advice perform optimization when there less load on cluster. mentioned optimization requires additional cpu, memory , disk space resources.
Comments
Post a Comment