No records should be dropped, regardless of if a commit or optimize is going on. Are you checking the return codes (HTTP return codes for Solr 1.3)? Some updates could be failing for some reason. Also grep for "Exception" in the solr log file.
-Yonik On Mon, Jun 16, 2008 at 4:02 PM, dls1138 <[EMAIL PROTECTED]> wrote: > > I've been sending data in batches to Solr with no errors reported, yet after > a commit, over 50% of the records I added (before the commit) do not show > up- even after several subsequent commits down the road. > > Is it possible that Solr/Lucene could be disregarding or dropping my add > queries if those queries were executed while a commit was running? > > For example, if I add 300 records, and then do a commit- during the 10-20 > seconds for the commit to execute (on an index over 1.2M records), if I add > 100 more records during that 10-20 second time period, are those adds lost? > I'm assuming they are not and will be visible after the next commit, but I > want to be sure as it seems that some are being dropped. I just need to know > if this can happen during commits or if I should be looking elsewhere to > resolve my dropped record problem. > > Thanks. > > > -- > View this message in context: > http://www.nabble.com/Adding-records-during-a-commit-tp17872257p17872257.html > Sent from the Solr - User mailing list archive at Nabble.com. > >
