Hi, I'm missing the bigger context of this thread here, but from the snippet below - sure, commits cause in-memory index to get written to disk, that causes some IO, and that *could* affect search *if* queries are running on the same box. When index and/or query volume is high, one typically puts indexing and searching on different servers.
Otis -- Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch ----- Original Message ---- > From: Steve Conover <scono...@gmail.com> > To: solr-user@lucene.apache.org > Sent: Thu, January 21, 2010 1:00:05 AM > Subject: Re: solr blocking on commit > > > How solr organized so that search can continue when a commit has closed the > > index? > > Also, looking at lucene docs, commit causes a system fsync(). Won't search > > also > > get blocked by the IO traffic generated? > > > ...I'll run iostat too and see if there's anything interesting to report
