It looks like (we don't have autocommit section in
solr.DirectUpdateHandler2, is ramBufferSizeMB is responsible for
that?):
<indexDefaults>
<useCompoundFile>false</useCompoundFile>
<mergeFactor>10</mergeFactor>
<ramBufferSizeMB>320</ramBufferSizeMB>
<maxMergeDocs>2147483647</maxMergeDocs>
<maxFieldLength>10000</maxFieldLength>
<writeLockTimeout>1000</writeLockTimeout>
<commitLockTimeout>10000</commitLockTimeout>
<lockType>single</lockType>
</indexDefaults>
<mainIndex>
<useCompoundFile>false</useCompoundFile>
<ramBufferSizeMB>320</ramBufferSizeMB>
<mergeFactor>10</mergeFactor>
<maxMergeDocs>2147483647</maxMergeDocs>
<maxFieldLength>10000</maxFieldLength>
<unlockOnStartup>false</unlockOnStartup>
</mainIndex>
<updateHandler class="solr.DirectUpdateHandler2">
<maxPendingDeletes>100000</maxPendingDeletes>
</updateHandler>
But as you said before slave replicates after commit, but in that case
shouldn't master be also updated with nex index? Our scripts showed
that master still has the old index (see my first email).
Thanks
2011/3/14 Markus Jelsma <markus.jel...@openindex.io>:
> In solrconfig there might be a autocommit section enabled.
>
> On Monday 14 March 2011 14:18:42 lame wrote:
>> I don't commit at all we use Dataimporter, but I have a feeling that
>> it could be done by DIH (autocommit is it possible)?
>>
>> 2011/3/14 Markus Jelsma <markus.jel...@openindex.io>:
>> > Do you commit to often? Slaves won't replicate if while master is
>> > indexing if you don't send commits. Can you only commit once the
>> > indexing finishes?
>> >
>> > On Monday 14 March 2011 14:04:51 lame wrote:
>> >> Hi guys,
>> >> I have master slave replication enabled. Slave is replicating every 3
>> >> minutes and I encourage problems while I'm performing full import
>> >> command on master (which takes about 7 minutes).
>> >> Slave repliacates partial index about 200k documents out of 700k.
>> >> After next repliacation full index is replicated successfully.
>> >> We wrote simple scripts which check how many docs are indexed both on
>> >> master and slave and turns out that at the same time while slave has
>> >> partial index - master has not been reload yet and has all documents
>> >> (from previous full index).
>> >> My question is what is the best way to avoid partial index on slaves -
>> >> Should I disable replication while indexing master or should i use
>> >> core swaping?
>> >>
>> >> Thanks.
>> >
>> > --
>> > Markus Jelsma - CTO - Openindex
>> > http://www.linkedin.com/in/markus17
>> > 050-8536620 / 06-50258350
>
> --
> Markus Jelsma - CTO - Openindex
> http://www.linkedin.com/in/markus17
> 050-8536620 / 06-50258350
>
