Hi Chris. My logs don't look anything like that. They look like HTTP requests. Am I looking in the wrong place?
Dave > -----Original Message----- > From: Chris Hostetter [mailto:[EMAIL PROTECTED] > Sent: Monday, October 08, 2007 5:02 PM > To: solr-user > Subject: RE: Availability Issues > > > : > Do the slow requests start after a commit? > : > : Based on the way the logs read, you could argue that point. > : The stream of POSTs end in the logs and then subsequent queries > : take longer to run, but it's hard to be sure there's a direct > : correlation. > > you would know based on the INFO level messages related to a > commit ... > you'll see messages that look like this when the commit starts... > > Oct 8, 2007 1:56:48 PM > org.apache.solr.update.DirectUpdateHandler2 commit > INFO: start commit(optimize=false,waitFlush=false,waitSearcher=true) > > ...then you'll see a message like this... > > Oct 8, 2007 1:56:48 PM > org.apache.solr.update.DirectUpdateHandler2 commit > INFO: end_commit_flush > > ...if you have autowarming you'll see a bunch of logs about > that, and then eventually you'll see a message like this... > > Oct 8, 2007 1:56:48 PM > org.apache.solr.update.processor.LogUpdateProcessor finish > INFO: {commit=} 0 299 > > ...the important question is how many of these hangs or > really long queries happen in the midst of all that ... how > many happen very quickly after it (which may indicate not > enough warming) > > (NOTE: some of those log messages may look different in your > nightly snapshot version, but the main gist should be the > same .. i don't remember when exactly the LogUpdateProcessor > was added). > > > > > -Hoss > > >
