Yes, the replication system sometimes leaves previous files. They do not get 'added' to the index. The 'segment' files describe which segment files are part of the index.
The query servers should have query caches turned on, and the indexer should have them turned off. Those and the replication servers are the only things I know of that should be different. The solr configuration files accept system properties and will substitute the values into the solrconfig.xml file: look at the solr.solr.dir variable. You can try having the same file everywhere and use different properties. Lance On Sun, Jan 9, 2011 at 4:39 AM, Roxana Angheluta <anghelu...@yahoo.com> wrote: > Sorry for the delay, Yahoo tagged my messages as spam and blocked them. I am > resending. > > The index seems ok on the master. > > In the meanwhile I manually ran a replication on one of the slaves and the > whole index got copied and "added" to the previous index. I had to manually > run RELOAD for that core to get rid of previous index files and have the same > size of the index directory as on the master. > > During the replication, how can the index get in an illegal state "committed"? > > Is it good practice to have the same solrconfig.xml on both master and slave, > with the exception of autoCommit and replication sections? > > Thanks a lot, > roxana > > > --- On Tue, 1/4/11, Lance Norskog <goks...@gmail.com> wrote: > >> From: Lance Norskog <goks...@gmail.com> >> Subject: Re: problems with replication >> To: solr-user@lucene.apache.org >> Date: Tuesday, January 4, 2011, 11:25 PM >> Are the index files corrupted? Lucene >> includes a program CheckIndex >> which will verify that the index data structures are not >> corrupted. >> >> Lance Norskog >> >> On Tue, Jan 4, 2011 at 7:50 AM, Roxana Angheluta <anghelu...@yahoo.com> >> wrote: >> > Thanks for replying. >> > >> > I am not able to reproduce it, it does not happen at >> every replication. >> > I just see the errors in the logs. >> > >> > At this point I have multiple errors in the logs and I >> am trying to analyze them systematically. See other examples >> below, this time from the slave. I suspect they are related >> and have to do with the replication. I used to have the >> server set-up as a repeater, now it is a simple slave. >> > >> > I don't really know where to start debugging, any >> advice is appreciated. >> > >> > roxana >> > >> > >> > Jan 4, 2011 5:06:22 AM >> sun.reflect.GeneratedMethodAccessor6 invoke >> > WARNING: Committed before 500 null >> > >> > org.mortbay.jetty.EofException >> > at >> org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:767) >> > at >> org.mortbay.jetty.AbstractGenerator$Output.flush(AbstractGenerator.java:562) >> > at >> org.mortbay.jetty.HttpConnection$Output.flush(HttpConnection.java:898) >> > at >> org.mortbay.jetty.AbstractGenerator$Output.blockForOutput(AbstractGenerator.java:528) >> > at >> org.mortbay.jetty.AbstractGenerator$Output.write(AbstractGenerator.java:619) >> > at >> org.mortbay.jetty.AbstractGenerator$Output.write(AbstractGenerator.java:573) >> > at >> org.apache.solr.common.util.FastOutputStream.flushBuffer(FastOutputStream.java:183) >> > at >> org.apache.solr.common.util.JavaBinCodec.marshal(JavaBinCodec.java:89) >> > at >> org.apache.solr.request.BinaryResponseWriter.write(BinaryResponseWriter.java:45) >> > at >> org.apache.solr.servlet.SolrDispatchFilter.writeResponse(SolrDispatchFilter.java:322) >> > at >> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:254) >> > at >> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) >> > at >> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) >> > at >> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) >> > at >> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) >> > at >> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) >> > at >> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) >> > at >> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) >> > >> > --------------------------------- >> > >> > java.lang.IllegalStateException: Committed >> > at >> org.mortbay.jetty.Response.resetBuffer(Response.java:972) >> > at >> org.mortbay.jetty.Response.sendError(Response.java:238) >> > at >> org.apache.solr.servlet.SolrDispatchFilter.sendError(SolrDispatchFilter.java:362) >> > at >> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:272) >> > at >> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) >> > at >> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) >> > at >> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) >> > at >> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) >> > at >> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) >> > at >> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) >> > at >> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) >> > at >> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) >> > at >> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) >> > at >> org.mortbay.jetty.Server.handle(Server.java:285) >> > at >> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502) >> > at >> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:835) >> > at >> org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:641) >> > at >> org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208) >> > at >> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378) >> > at >> org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226) >> > at >> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) >> > >> > >> > --- On Mon, 1/3/11, Grant Ingersoll <gsing...@apache.org> >> wrote: >> > >> >> From: Grant Ingersoll <gsing...@apache.org> >> >> Subject: Re: problems with replication >> >> To: solr-user@lucene.apache.org >> >> Date: Monday, January 3, 2011, 4:20 PM >> >> Are you able to reproduce this? >> >> Can you give more details on what is happening? >> Does >> >> this happen every time you replicate? >> >> >> >> On Dec 29, 2010, at 3:11 PM, Roxana Angheluta >> wrote: >> >> >> >> > Hi, >> >> > >> >> > What can cause the following error on the >> master - >> >> stack trace below. >> >> > The slave is stuck in the middle of >> replication until >> >> manual intervention and responds very slow to >> searches. >> >> > >> >> > Thanks, >> >> > roxana >> >> > > > > > > -- Lance Norskog goks...@gmail.com
