Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Duplicate
-
2.4.1
-
None
-
New
Description
Basically I'm trying to create largish 2-4GB shards using
LogByteSizeMergePolicy, however I've found in the attached unit
test segments that exceed maxMergeMB.
The goal is for segments to be merged up to 2GB, then all
merging to that segment stops, and then another 2GB segment is
created. This helps when replicating in Solr where if a single
optimized 60GB segment is created, the machine stops working due
to IO and CPU starvation.