Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 17 May 2012 01:10:09 +0000 (UTC)
From: "Michael Garski (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <407444049.6878.1337217009773.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (SOLR-3465) Replication Causes Two Searcher
 Warmups
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Michael Garski created SOLR-3465:
------------------------------------

             Summary: Replication Causes Two Searcher Warmups 
                 Key: SOLR-3465
                 URL: https://issues.apache.org/jira/browse/SOLR-3465
             Project: Solr
          Issue Type: Bug
          Components: replication (java)
    Affects Versions: 4.0
            Reporter: Michael Garski


I'm doing some testing with the current trunk, and am seeing that when a slave retrieves index updates from the master the warmup & searcher registration is performed twice.  Here is a snippet of the log that demonstrates this:

May 16, 2012 6:02:02 PM org.apache.solr.handler.SnapPuller fetchLatestIndex
INFO: Total time taken for download : 92 secs
May 16, 2012 6:02:02 PM org.apache.solr.core.SolrDeletionPolicy onInit
INFO: SolrDeletionPolicy.onInit: commits:num=2
        commit{dir=/Users/mgarski/Code/indexes/solr2/geo/index,segFN=segments_1,generation=1,filenames=[segments_1]
        commit{dir=/Users/mgarski/Code/indexes/solr2/geo/index,segFN=segments_10,generation=36,filenames=[_45_0.tim, _45.fdt, segments_10, _45_0.tip, _45.fdx, _45.fnm, _45_0.frq, _45.per, _45_0.prx]
May 16, 2012 6:02:02 PM org.apache.solr.core.SolrDeletionPolicy updateCommits
INFO: newest commit = 36
May 16, 2012 6:02:02 PM org.apache.solr.search.SolrIndexSearcher <init>
INFO: Opening Searcher@559fe5e6 main
May 16, 2012 6:02:02 PM org.apache.solr.core.QuerySenderListener newSearcher
INFO: QuerySenderListener sending requests to Searcher@559fe5e6 main{StandardDirectoryReader(segments_10:335:nrt _45(4.0):C1096375)}
May 16, 2012 6:02:02 PM org.apache.solr.core.QuerySenderListener newSearcher
INFO: QuerySenderListener done.
May 16, 2012 6:02:02 PM org.apache.solr.core.SolrCore registerSearcher
INFO: [geo] Registered new searcher Searcher@559fe5e6 main{StandardDirectoryReader(segments_10:335:nrt _45(4.0):C1096375)}
May 16, 2012 6:02:02 PM org.apache.solr.update.DirectUpdateHandler2 commit
INFO: start commit{flags=0,version=0,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false}
May 16, 2012 6:02:02 PM org.apache.solr.search.SolrIndexSearcher <init>
INFO: Opening Searcher@42101da9 main
May 16, 2012 6:02:02 PM org.apache.solr.update.DirectUpdateHandler2 commit
INFO: end_commit_flush
May 16, 2012 6:02:02 PM org.apache.solr.core.QuerySenderListener newSearcher
INFO: QuerySenderListener sending requests to Searcher@42101da9 main{StandardDirectoryReader(segments_10:335:nrt _45(4.0):C1096375)}
May 16, 2012 6:02:02 PM org.apache.solr.core.QuerySenderListener newSearcher
INFO: QuerySenderListener done.
May 16, 2012 6:02:02 PM org.apache.solr.core.SolrCore registerSearcher
INFO: [geo] Registered new searcher Searcher@42101da9 main{StandardDirectoryReader(segments_10:335:nrt _45(4.0):C1096375)}

I am trying to determine the cause, does anyone have any idea where to start?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org