Or time.
<!--autocommit pending docs if certain criteria are met -->
<autoCommit> <maxDocs>10000</maxDocs> <maxTime>10000</maxTime>
</autoCommit>
> Date: Thu, 7 Aug 2008 18:42:30 -0300> From: [EMAIL PROTECTED]> To:
> solr-user@lucene.apache.org> Subject: Re: How do I configure commit to run
> after updates> > You can configure the autocommit feature in solrconfig.xml
> to get commit to> work from time to time or based in the number of documents
> added to your> index.> > 2008/8/7 Jacob Singh <[EMAIL PROTECTED]>> > > Hi,>
> >> > I'm using the XML based update interface, and feeding requests to
> update> > the index via jetty. It all works great, however now I'm trying to
> get> > replication running, and here's what I understand:> >> > 1. An index
> update comes in.> > 2. Solr runs the commit script> > 3. a post-commit event
> is specified in solrconfig.xml:> >> > <listener event="postCommit"
> class="solr.RunExecutableListener">> > <str name="exe">snapshooter</str>> >
> ....> >> > 4. This creates a snapshot of the index and puts it in
> data/SNAPSHOT...> > 5. The slaves run on cron, ssh in to the master, and
> basically just ls> > the data dir, find if there is a new snapshot and rsync
> it> > 6. the slaves "warm" the index and swap it.> > 7. snapcleaner runs on
> both machines to clear out old snapshots.> >> > Okay... so this all makes
> sense, and I can sorta make it work, however,> > the commit is never run by
> itself when the index is updated. I have to> > manually call the commit
> script from the command line to get it to happen.> >> > Do I have to call
> something additional via the webservice?> >> > Am I missing a config option
> in solrconfig.xml? (I'm using the example,> > so I wouldn't think so).> >> >
> Thanks a lot!> > Jacob> >> > > > -- > Alexander Ramos Jardim
_________________________________________________________________
Chose your Life Partner? Join MSN Matrimony FREE
http://www.shaadi.com/msn/matrimony.php
