lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharath Venkatesh" <>
Subject RE: latency in solr response is observed after index is updated
Date Tue, 01 Dec 2009 10:13:30 GMT
Hi Kalidoss,
   I am not aware of using solr-config for committing the document . 
but I have mentioned below how we update and  commit documents:
curl http://solr_url/update --data-binary @feeds.xml -H 
'Content-type:text/xml; charset=utf-8'
curl http://solr_url/update --data-binary '<commit/>' -H 
'Content-type:text/xml; charset=utf-8'

where feeds.xml contains the document in xml format

we have master and slave replication for solr server.

updates happens in master , snappuller and snapinstaller is run on 
slaves periodically
queries don't happen at master , only happens at slaves

is there any thing which can be said from above information ?


-----Original Message-----
From: kalidoss []
Sent: Tue 12/1/2009 2:38 PM
Subject: Re: latency in solr response  is observed  after index is updated
r u using solr-config for committing the document?

bharath venkatesh wrote:
> Hi,
>     We are observing latency (some times huge latency upto 10-20 secs) 
> in solr response  after index is updated . whats the reason of this 
> latency and how can it be minimized ?
> Note: our index size is pretty large.
> any help would be appreciated as we largely affected by it
> Thanks in advance.
> Bharath

This message is intended only for the use of the addressee and may contain information that
is privileged, confidential 
and exempt from disclosure under applicable law. If the reader of this message is not the
intended recipient, or the 
employee or agent responsible for delivering the message to the intended recipient, you are
hereby notified that any 
dissemination, distribution or copying of this communication is strictly prohibited. If you
have received this e-mail 
in error, please notify us immediately by return e-mail and delete this e-mail and all attachments
from your system.

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message