Locking is at a lower level than indexing and queries. Solr coordinates multi-threaded indexing and query operations in memory and a separate thread writes data to disk. There are no performance problems with multiple searches and indexes happening at the same time.
2010/3/2 Kranti™ K K Parisa <kranti.par...@gmail.com>: > and also about the time when two update requests come at the same time. Then > whichever request comes first will be updating the index while other > requests wait until the locktimeout that we have configured?? > > > Best Regards, > Kranti K K Parisa > > > > 2010/3/2 Kranti™ K K Parisa <kranti.par...@gmail.com> > >> Hi Ron, >> >> Thanks for the reply. So does this mean that writer lock is nothing to do >> with concurrent writes? >> >> Best Regards, >> Kranti K K Parisa >> >> >> >> On Tue, Mar 2, 2010 at 4:19 PM, Ron Chan <rc...@i-tao.com> wrote: >> >>> as long as the document id is unique, concurrent writes is fine >>> >>> if for same reason the same doc id is used then it is overwritten, so last >>> in will be the one that is in the index >>> >>> Ron >>> >>> ----- Original Message ----- >>> From: "Kranti™ K K Parisa" <kranti.par...@gmail.com> >>> To: solr-user@lucene.apache.org >>> Sent: Tuesday, 2 March, 2010 10:40:37 AM >>> Subject: Simultaneous Writes to Index >>> >>> Hi, >>> >>> I am planning to development some application on which users could update >>> their account data after login, this is on top of the search facility >>> users >>> have. the basic work flow is >>> 1) user logs in >>> 2) searches for some data >>> 3) gets the results from solr index >>> 4) save some of the search results into their repository >>> 5) later on they may view their repository >>> >>> for this, at step4 I am planning to write that into a separate solr index >>> as >>> user may search within his repository and get the results, facets..etc. >>> So thinking to write such data/info to a separate solr index. >>> >>> in this plan, how simultaneous writes to the user history index works. >>> what >>> are the best practices in such scenarios of updating index at a time by >>> different users. >>> >>> the other alternative is to store such user info into DB, and schedule >>> indexing process at regular intervals. But that wont make the system live >>> with user actions, as there would be some delay, users cant see the data >>> they saved in their repository until its indexed. >>> >>> that is the reason I am planning to use SOLR xml post request to update >>> the >>> index silently but how about multiple users writing on same index? >>> >>> Best Regards, >>> Kranti K K Parisa >>> >> >> > -- Lance Norskog goks...@gmail.com
