Another note.. if I reload solr app it goes back down in size.
here is my replication settings on the master:
<requestHandler name="/replication" class="solr.ReplicationHandler" >
<lst name="master">
<str name="replicateAfter">startup</str>
<str name="replicateAfter">commit</str>
<str name="replicateAfter">optimize</str>
<int name="numberToKeep">1</int>
<str name="confFiles">schema.xml,stopwords.txt,elevate.xml</str>
<str name="commitReserveDuration">00:00:30</str>
</lst>
</requestHandler>
On Wed, Mar 14, 2012 at 3:54 PM, Mike Austin <mike.aus...@juggle.com> wrote:
> The odd thing is that if I optimize the index it doubles in size.. If I
> then, add one more document to the index it goes back down to half size?
>
> Is there a way to force this without needing to wait until another
> document is added? Or do you have more information on what you think is
> going on? I'm using a trunk version of solr4 from 9/12/2011 with a master
> with two slaves setup. Everything besides this is working great!
>
> Thanks,
> Mike
>
>
> On Tue, Mar 13, 2012 at 9:32 PM, Li Li <fancye...@gmail.com> wrote:
>
>> optimize will generate new segments and delete old ones. if your master
>> also provides searching service during indexing, the old files may be
>> opened by old SolrIndexSearcher. they will be deleted later. So when
>> indexing, the index size may double. But a moment later, old indexes will
>> be deleted.
>>
>> On Wed, Mar 14, 2012 at 7:06 AM, Mike Austin <mike.aus...@juggle.com>
>> wrote:
>>
>> > I have a master with two slaves. For some reason on the master if I do
>> an
>> > optimize after indexing on the master it double in size from 42meg to 90
>> > meg.. however, when the slaves replicate they get the 42meg index..
>> >
>> > Should the master and slaves always be the same size?
>> >
>> > Thanks,
>> > Mike
>> >
>>
>
>
