lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] Commented: (LUCENE-1750) Create a MergePolicy that limits the maximum size of it's segments
Date Tue, 21 Jul 2009 18:16:14 GMT


Shai Erera commented on LUCENE-1750:

bq. I think we can refine this to only merge contiguous segments that are sharing doc stores

So in this case it means that segment A will remain smaller than 4 GB and will never get merged
(b/c segments B and C reached their limit)?

> Create a MergePolicy that limits the maximum size of it's segments
> ------------------------------------------------------------------
>                 Key: LUCENE-1750
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>    Affects Versions: 2.4.1
>            Reporter: Jason Rutherglen
>            Priority: Minor
>             Fix For: 3.1
>         Attachments: LUCENE-1750.patch
>   Original Estimate: 48h
>  Remaining Estimate: 48h
> 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. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message