Yes this should reduce transient (while merging) disk usage.
However, optimize disregards this parameter, so it will still use the
same disk space. However, if you call optimize(N) then that should
use less space since it does not merge all the way down to 1 segment.
Note that the limit applies to segments-to-be-merged not to the final
merged segment size. Ie, any segment > maxMergeMB will never be
merged, but at any given time you can easily have segments quite a
bit larger than maxMergeMB.
Mike
Mark Miller wrote:
If I use LogByteSizeMergePolicy#setMaxMergeMB, can I clamp down on
the space needed for optimize/merge? My thought is, if a segment is
maxed out, it will never need to be copied for a merge right? So
you could significantly reduce merge/optimize space requirments
(now at like 2x-4x if readers can still open)?
- Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
