[
https://issues.apache.org/jira/browse/SOLR-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462233#comment-13462233
]
Hoss Man commented on SOLR-3884:
--------------------------------
The crux of hte issue i (think i) see is that the smoke tester tries to sanity
check the same example dir twice in succession, once with java6 and once with
java7. in sarowe's case, it's always the java7 version that fails (if it
fails) and here are some interesting tidbits from the output/log he posted...
{noformat}
test solr example w/ Java 6...
start Solr instance
(log=/home/sarowe/temp/tmpDir/unpack/apache-solr-4.0.0/solr-example.log)...
startup done
test utf8...
index example docs...
run query...
stop server (SIGINT)...
test solr example w/ Java 7...
start Solr instance
(log=/home/sarowe/temp/tmpDir/unpack/apache-solr-4.0.0/solr-example.log)...
startup done
test utf8...
index example docs...
run query...
FAILED: response is:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader"><int name="status">0</int><int
name="QTime">0</int><lst name="params"><str
name="q">video</str></lst></lst><result name="response" numFound="0"
start="0"></result>
</response>
{noformat}
So the requests to index & query data all succced, but the results are not what
is expected (no docs found for a simple query)
Then we look at the log from that failed second run o the example...
{noformat}
...
INFO: registering core: collection1
Sep 24, 2012 2:08:58 PM org.apache.solr.update.UpdateLog$LogReplayer doReplay
WARNING: Starting log replay
tlog{file=solr\collection1\data\tlog\tlog.0000000000000000000 refcount=2}
active=false
starting pos=0
Sep 24, 2012 2:08:58 PM org.apache.solr.servlet.SolrDispatchFilter init
INFO:
user.dir=C:\cygwin\home\sarowe\temp\tmpDir\unpack\apache-solr-4.0.0\example
Sep 24, 2012 2:08:58 PM org.apache.solr.servlet.SolrDispatchFilter init
INFO: SolrDispatchFilter.init() done
2012-09-24 14:08:58.105:INFO:oejs.AbstractConnector:Started
SocketConnector@0.0.0.0:8983
Sep 24, 2012 2:08:58 PM org.apache.solr.core.SolrDeletionPolicy onInit
INFO: SolrDeletionPolicy.onInit: commits:num=1
commit{dir=NRTCachingDirectory(org.apache.lucene.store.MMapDirectory@C:\cygwin\home\sarowe\temp\tmpDir\unpac
k\apache-solr-4.0.0\example\solr\collection1\data\index
lockFactory=org.apache.lucene.store.NativeFSLockFactory@7ea69d83;
maxCacheMB=48.0
maxMergeSizeMB=4.0),segFN=segments_1,generation=1,filenames=[segments_1]
Sep 24, 2012 2:08:58 PM org.apache.solr.core.SolrDeletionPolicy updateCommits
INFO: newest commit = 1
Sep 24, 2012 2:08:58 PM org.apache.solr.update.DirectUpdateHandler2 commit
INFO: start
commit{flags=2,_version_=0,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false}
Sep 24, 2012 2:08:58 PM org.apache.solr.core.SolrCore execute
INFO: [collection1] webapp=/solr path=/select
params={wt=python&q=hello¶ms=explicit} hits=0 status=0 QTime=1
Sep 24, 2012 2:08:58 PM org.apache.solr.core.SolrCore execute
...
{noformat}
...so we have astartup detecting things in the transaction log that need to be
replayed, and a commit starts -- meanwhile requests fro mthe smoke script
(checking utf8) are comming in. After that we start getting real example
documents...
{noformat}
...
INFO: [collection1] webapp=/solr path=/update params={}
{add=[EN7800GTX/2DHTV/256M (1414015368091926528), 100-435805
(1414015368095072256)]} 0 6
Sep 24, 2012 2:08:59 PM
org.apache.solr.update.processor.DistributedUpdateProcessor processCommit
INFO: Ignoring commit while not ACTIVE - state: REPLAYING replay:0
Sep 24, 2012 2:08:59 PM org.apache.solr.update.processor.LogUpdateProcessor
finish
INFO: [collection1] webapp=/solr path=/update params={softCommit=true}
{commit=} 0 1
Sep 24, 2012 2:08:59 PM org.apache.solr.core.SolrCore execute
INFO: [collection1] webapp=/solr path=/select/ params={q=video} hits=0 status=0
QTime=0
...
{noformat}
...and that's where things look wonky to me -- the smoke script explicitly sent
in a bunch of documents, and asked for a commit, but aparently even though the
client was given a success response, that commit was evidently ignored because
solr was in "REPLAYING" mode, so then the subsequent query didn't find the docs
it was expecting.
> possible bug in how commits are handled during "recovery" mode on startup?
> --------------------------------------------------------------------------
>
> Key: SOLR-3884
> URL: https://issues.apache.org/jira/browse/SOLR-3884
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
>
> while testing out 4.0-rc0, sarowe noted the he was seeing the smoke tester
> script fail while sanity checking the solr example.
> https://mail-archives.apache.org/mod_mbox/lucene-dev/201209.mbox/%3c6c78e97c707b5b4c8cc61d44f87545863ed...@suex10-mbx-03.ad.syr.edu%3E
> I'm not certain, but looking at his logs, i think this suggests a bug in how
> commits are handled when a newly started server is in "recovery" mode
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
