Re: Index fetch failed
Shankar: Two things: 1> please do not hijack threads 2> Follow the instructions here: http://lucene.apache.org/solr/community.html#mailing-lists-irc. You must use the _exact_ same e-mail as you used to subscribe. If the initial try doesn't work and following the suggestions at the "problems" link doesn't work for you, let us know. But note you need to show us the _entire_ return header to allow anyone to diagnose the problem. Best, Erick > On Sep 3, 2019, at 5:55 AM, Shankar Ramalingam wrote: > > Please remove my email id from this list. > > On Tue, 3 Sep, 2019, 11:06 AM Akreeti Agarwal, wrote: > >> Hello, >> >> Please help me with the solution for below error. >> >> Memory details of slave server: >> total used free sharedbuffers cached >> Mem: 15947 15460487 62144 6007 >> -/+ buffers/cache: 9308 6639 >> Swap:0 0 0 >> >> >> Thanks & Regards, >> Akreeti Agarwal >> >> -Original Message- >> From: Akreeti Agarwal >> Sent: Wednesday, August 28, 2019 2:45 PM >> To: solr-user@lucene.apache.org >> Subject: RE: Index fetch failed >> >> Yes I am using solr-5.5.5. >> This error is intermittent. I don't think there must be any issue with >> master connection limits. This error is accompanied by this on master side: >> >> ERROR (qtp1450821318-60072) [ x:sitecore_web_index] >> o.a.s.h.ReplicationHandler Unable to get file names for indexCommit >> generation: 1558637 >> java.nio.file.NoSuchFileException: >> /solrm-efs/solr-m/server/solr/sitecore_web_index/data/index/_12i9p_1.liv >> at >> sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) >> at >> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) >> at >> sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) >> at >> sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55) >> at >> sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:144) >> at >> sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:99) >> at java.nio.file.Files.readAttributes(Files.java:1737) >> at java.nio.file.Files.size(Files.java:2332) >> at >> org.apache.lucene.store.FSDirectory.fileLength(FSDirectory.java:210) >> at >> org.apache.lucene.store.NRTCachingDirectory.fileLength(NRTCachingDirectory.java:124) >> at >> org.apache.solr.handler.ReplicationHandler.getFileList(ReplicationHandler.java:563) >> at >> org.apache.solr.handler.ReplicationHandler.handleRequestBody(ReplicationHandler.java:253) >> at >> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:155) >> at org.apache.solr.core.SolrCore.execute(SolrCore.java:2102) >> at >> org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:654) >> at >> org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:460) >> at >> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:257) >> at >> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:208) >> at >> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) >> at >> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) >> at >> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) >> at >> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577) >> at >> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) >> at >> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) >> at >> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) >> at >> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) >> at >> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) >> at >> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) >> at >> org.eclipse.jetty.server.handle
Re: Index fetch failed
Please remove my email id from this list. On Tue, 3 Sep, 2019, 11:06 AM Akreeti Agarwal, wrote: > Hello, > > Please help me with the solution for below error. > > Memory details of slave server: > total used free sharedbuffers cached > Mem: 15947 15460487 62144 6007 > -/+ buffers/cache: 9308 6639 > Swap:0 0 0 > > > Thanks & Regards, > Akreeti Agarwal > > -Original Message- > From: Akreeti Agarwal > Sent: Wednesday, August 28, 2019 2:45 PM > To: solr-user@lucene.apache.org > Subject: RE: Index fetch failed > > Yes I am using solr-5.5.5. > This error is intermittent. I don't think there must be any issue with > master connection limits. This error is accompanied by this on master side: > > ERROR (qtp1450821318-60072) [ x:sitecore_web_index] > o.a.s.h.ReplicationHandler Unable to get file names for indexCommit > generation: 1558637 > java.nio.file.NoSuchFileException: > /solrm-efs/solr-m/server/solr/sitecore_web_index/data/index/_12i9p_1.liv >at > sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) >at > sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) >at > sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) >at > sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55) >at > sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:144) >at > sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:99) >at java.nio.file.Files.readAttributes(Files.java:1737) >at java.nio.file.Files.size(Files.java:2332) >at > org.apache.lucene.store.FSDirectory.fileLength(FSDirectory.java:210) >at > org.apache.lucene.store.NRTCachingDirectory.fileLength(NRTCachingDirectory.java:124) >at > org.apache.solr.handler.ReplicationHandler.getFileList(ReplicationHandler.java:563) >at > org.apache.solr.handler.ReplicationHandler.handleRequestBody(ReplicationHandler.java:253) >at > org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:155) >at org.apache.solr.core.SolrCore.execute(SolrCore.java:2102) >at > org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:654) >at > org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:460) >at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:257) >at > org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:208) >at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) >at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) >at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) >at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577) >at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) >at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) >at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) >at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) >at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) >at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) >at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) >at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110) >at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) >at org.eclipse.jetty.server.Server.handle(Server.java:499) >at > org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) >at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) >at org.eclipse.jetty.io > .AbstractConnection$2.run(AbstractConnection.java:540) >at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) >at > org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.ja
RE: Index fetch failed
Hello, Please help me with the solution for below error. Memory details of slave server: total used free sharedbuffers cached Mem: 15947 15460487 62144 6007 -/+ buffers/cache: 9308 6639 Swap:0 0 0 Thanks & Regards, Akreeti Agarwal -Original Message- From: Akreeti Agarwal Sent: Wednesday, August 28, 2019 2:45 PM To: solr-user@lucene.apache.org Subject: RE: Index fetch failed Yes I am using solr-5.5.5. This error is intermittent. I don't think there must be any issue with master connection limits. This error is accompanied by this on master side: ERROR (qtp1450821318-60072) [ x:sitecore_web_index] o.a.s.h.ReplicationHandler Unable to get file names for indexCommit generation: 1558637 java.nio.file.NoSuchFileException: /solrm-efs/solr-m/server/solr/sitecore_web_index/data/index/_12i9p_1.liv at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55) at sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:144) at sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:99) at java.nio.file.Files.readAttributes(Files.java:1737) at java.nio.file.Files.size(Files.java:2332) at org.apache.lucene.store.FSDirectory.fileLength(FSDirectory.java:210) at org.apache.lucene.store.NRTCachingDirectory.fileLength(NRTCachingDirectory.java:124) at org.apache.solr.handler.ReplicationHandler.getFileList(ReplicationHandler.java:563) at org.apache.solr.handler.ReplicationHandler.handleRequestBody(ReplicationHandler.java:253) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:155) at org.apache.solr.core.SolrCore.execute(SolrCore.java:2102) at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:654) at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:460) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:257) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:208) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:499) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) at java.lang.Thread.run(Thread.java:748) Thanks & Regards, Akreeti Agarwal -Original Message- From: Atita Arora Sent: Wednesday, August 28, 2019 2:23 PM To: solr-user@lucene.apache.org Subject: Re: Index fetch failed This looks like ample memory to get the index chunk. Also, I looked at the IndexFetcher code, I remember you were using Solr 5.5.5 and the only reason in my view, this would happen is when the index chunk is not downloaded as can also be seen in the error (Downloaded 0!=123) which clearl
RE: Index fetch failed
Yes I am using solr-5.5.5. This error is intermittent. I don't think there must be any issue with master connection limits. This error is accompanied by this on master side: ERROR (qtp1450821318-60072) [ x:sitecore_web_index] o.a.s.h.ReplicationHandler Unable to get file names for indexCommit generation: 1558637 java.nio.file.NoSuchFileException: /solrm-efs/solr-m/server/solr/sitecore_web_index/data/index/_12i9p_1.liv at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55) at sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:144) at sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:99) at java.nio.file.Files.readAttributes(Files.java:1737) at java.nio.file.Files.size(Files.java:2332) at org.apache.lucene.store.FSDirectory.fileLength(FSDirectory.java:210) at org.apache.lucene.store.NRTCachingDirectory.fileLength(NRTCachingDirectory.java:124) at org.apache.solr.handler.ReplicationHandler.getFileList(ReplicationHandler.java:563) at org.apache.solr.handler.ReplicationHandler.handleRequestBody(ReplicationHandler.java:253) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:155) at org.apache.solr.core.SolrCore.execute(SolrCore.java:2102) at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:654) at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:460) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:257) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:208) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:499) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) at java.lang.Thread.run(Thread.java:748) Thanks & Regards, Akreeti Agarwal -Original Message- From: Atita Arora Sent: Wednesday, August 28, 2019 2:23 PM To: solr-user@lucene.apache.org Subject: Re: Index fetch failed This looks like ample memory to get the index chunk. Also, I looked at the IndexFetcher code, I remember you were using Solr 5.5.5 and the only reason in my view, this would happen is when the index chunk is not downloaded as can also be seen in the error (Downloaded 0!=123) which clearly states that the index generations are not in sync and this is not user aborted action too. Is this error intermittent? could there be a possibility that your master has connection limits? or maybe some network hiccup? On Wed, Aug 28, 2019 at 10:40 AM Akreeti Agarwal wrote: > Hi, > > Memory details for slave1: > > Filesystem Size Used Avail Use% Mounted on > /dev/xvda1 99G 40G 55G 43% / > tmpfs 7.8G 0 7.8G 0% /dev/shm > > Memory det
Re: Index fetch failed
This looks like ample memory to get the index chunk. Also, I looked at the IndexFetcher code, I remember you were using Solr 5.5.5 and the only reason in my view, this would happen is when the index chunk is not downloaded as can also be seen in the error (Downloaded 0!=123) which clearly states that the index generations are not in sync and this is not user aborted action too. Is this error intermittent? could there be a possibility that your master has connection limits? or maybe some network hiccup? On Wed, Aug 28, 2019 at 10:40 AM Akreeti Agarwal wrote: > Hi, > > Memory details for slave1: > > Filesystem Size Used Avail Use% Mounted on > /dev/xvda1 99G 40G 55G 43% / > tmpfs 7.8G 0 7.8G 0% /dev/shm > > Memory details for slave2: > > Filesystem Size Used Avail Use% Mounted on > /dev/xvda1 99G 45G 49G 48% / > tmpfs 7.8G 0 7.8G 0% /dev/shm > > Thanks & Regards, > Akreeti Agarwal > > -Original Message- > From: Atita Arora > Sent: Wednesday, August 28, 2019 11:15 AM > To: solr-user@lucene.apache.org > Subject: Re: Index fetch failed > > Hii, > > Do you have enough memory free for the index chunk to be > fetched/Downloaded on the slave node? > > > On Wed, Aug 28, 2019 at 6:57 AM Akreeti Agarwal wrote: > > > Hello Everyone, > > > > I am getting this error continuously on Solr slave, can anyone tell me > > the solution for this: > > > > 642141666 ERROR (indexFetcher-72-thread-1) [ x:sitecore_web_index] > > o.a.s.h.ReplicationHandler Index fetch failed > > :org.apache.solr.common.SolrException: Unable to download _12i7v_f.liv > > completely. Downloaded 0!=123 > > at > > > org.apache.solr.handler.IndexFetcher$FileFetcher.cleanup(IndexFetcher.java:1434) > > at > > > org.apache.solr.handler.IndexFetcher$FileFetcher.fetchFile(IndexFetcher.java:1314) > > at > > > org.apache.solr.handler.IndexFetcher.downloadIndexFiles(IndexFetcher.java:812) > > at > > org.apache.solr.handler.IndexFetcher.fetchLatestIndex(IndexFetcher.jav > > a:427) > > > > > > Thanks & Regards, > > Akreeti Agarwal > > (M) +91-8318686601 > > > > ::DISCLAIMER:: > > > > -- > > -- > > -- > > > > The contents of this e-mail and any attachment(s) are confidential and > > intended for the named recipient(s) only. E-mail transmission is not > > guaranteed to be secure or error-free as information could be > > intercepted, corrupted, lost, destroyed, arrive late or incomplete, or > > may contain viruses in transmission. The e mail and its contents (with > > or without referred errors) shall therefore not attach any liability > > on the originator or HCL or its affiliates. Views or opinions, if any, > > presented in this email are solely those of the author and may not > > necessarily reflect the views or opinions of HCL or its affiliates. > > Any form of reproduction, dissemination, copying, disclosure, > > modification, distribution and / or publication of this message > > without the prior written consent of authorized representative of HCL > > is strictly prohibited. If you have received this email in error > > please delete it and notify the sender immediately. Before opening any > > email and/or attachments, please check them for viruses and other > defects. > > > > -- > > > > > >
RE: Index fetch failed
Hi, Memory details for slave1: Filesystem Size Used Avail Use% Mounted on /dev/xvda1 99G 40G 55G 43% / tmpfs 7.8G 0 7.8G 0% /dev/shm Memory details for slave2: Filesystem Size Used Avail Use% Mounted on /dev/xvda1 99G 45G 49G 48% / tmpfs 7.8G 0 7.8G 0% /dev/shm Thanks & Regards, Akreeti Agarwal -Original Message- From: Atita Arora Sent: Wednesday, August 28, 2019 11:15 AM To: solr-user@lucene.apache.org Subject: Re: Index fetch failed Hii, Do you have enough memory free for the index chunk to be fetched/Downloaded on the slave node? On Wed, Aug 28, 2019 at 6:57 AM Akreeti Agarwal wrote: > Hello Everyone, > > I am getting this error continuously on Solr slave, can anyone tell me > the solution for this: > > 642141666 ERROR (indexFetcher-72-thread-1) [ x:sitecore_web_index] > o.a.s.h.ReplicationHandler Index fetch failed > :org.apache.solr.common.SolrException: Unable to download _12i7v_f.liv > completely. Downloaded 0!=123 > at > org.apache.solr.handler.IndexFetcher$FileFetcher.cleanup(IndexFetcher.java:1434) > at > org.apache.solr.handler.IndexFetcher$FileFetcher.fetchFile(IndexFetcher.java:1314) > at > org.apache.solr.handler.IndexFetcher.downloadIndexFiles(IndexFetcher.java:812) > at > org.apache.solr.handler.IndexFetcher.fetchLatestIndex(IndexFetcher.jav > a:427) > > > Thanks & Regards, > Akreeti Agarwal > (M) +91-8318686601 > > ::DISCLAIMER:: > > -- > -- > -- > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. E-mail transmission is not > guaranteed to be secure or error-free as information could be > intercepted, corrupted, lost, destroyed, arrive late or incomplete, or > may contain viruses in transmission. The e mail and its contents (with > or without referred errors) shall therefore not attach any liability > on the originator or HCL or its affiliates. Views or opinions, if any, > presented in this email are solely those of the author and may not > necessarily reflect the views or opinions of HCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, > modification, distribution and / or publication of this message > without the prior written consent of authorized representative of HCL > is strictly prohibited. If you have received this email in error > please delete it and notify the sender immediately. Before opening any > email and/or attachments, please check them for viruses and other defects. > > -- > >
Re: Index fetch failed
Hii, Do you have enough memory free for the index chunk to be fetched/Downloaded on the slave node? On Wed, Aug 28, 2019 at 6:57 AM Akreeti Agarwal wrote: > Hello Everyone, > > I am getting this error continuously on Solr slave, can anyone tell me the > solution for this: > > 642141666 ERROR (indexFetcher-72-thread-1) [ x:sitecore_web_index] > o.a.s.h.ReplicationHandler Index fetch failed > :org.apache.solr.common.SolrException: Unable to download _12i7v_f.liv > completely. Downloaded 0!=123 > at > org.apache.solr.handler.IndexFetcher$FileFetcher.cleanup(IndexFetcher.java:1434) > at > org.apache.solr.handler.IndexFetcher$FileFetcher.fetchFile(IndexFetcher.java:1314) > at > org.apache.solr.handler.IndexFetcher.downloadIndexFiles(IndexFetcher.java:812) > at > org.apache.solr.handler.IndexFetcher.fetchLatestIndex(IndexFetcher.java:427) > > > Thanks & Regards, > Akreeti Agarwal > (M) +91-8318686601 > > ::DISCLAIMER:: > > -- > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. E-mail transmission is not > guaranteed to be secure or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or may contain > viruses in transmission. The e mail and its contents (with or without > referred errors) shall therefore not attach any liability on the originator > or HCL or its affiliates. Views or opinions, if any, presented in this > email are solely those of the author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, distribution and / or > publication of this message without the prior written consent of authorized > representative of HCL is strictly prohibited. If you have received this > email in error please delete it and notify the sender immediately. Before > opening any email and/or attachments, please check them for viruses and > other defects. > > -- >
Index fetch failed
Hello Everyone, I am getting this error continuously on Solr slave, can anyone tell me the solution for this: 642141666 ERROR (indexFetcher-72-thread-1) [ x:sitecore_web_index] o.a.s.h.ReplicationHandler Index fetch failed :org.apache.solr.common.SolrException: Unable to download _12i7v_f.liv completely. Downloaded 0!=123 at org.apache.solr.handler.IndexFetcher$FileFetcher.cleanup(IndexFetcher.java:1434) at org.apache.solr.handler.IndexFetcher$FileFetcher.fetchFile(IndexFetcher.java:1314) at org.apache.solr.handler.IndexFetcher.downloadIndexFiles(IndexFetcher.java:812) at org.apache.solr.handler.IndexFetcher.fetchLatestIndex(IndexFetcher.java:427) Thanks & Regards, Akreeti Agarwal (M) +91-8318686601 ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. --
Re: Index fetch failed. Exception: Server refused connection
A 1 Gb heap is probably too small on the master. Run with 8 Gb like the slaves.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Oct 24, 2018, at 10:20 PM, Bharat Yadav wrote:
>
> Hello Team,
>
> We are now a days frequently facing below issue on our SOLR Slave Nodes
> related to public Class SnapPuller.
>
> Issue
>
> Master at: http://prd01slr:3/solr/MainSystem2
> <http://prd01slr:3/solr/MainSystem2> is not available. Index fetch
> failed. Exception: Server refused connection at:
> http://prd01slr:3/solr/MainSystem2
> <http://prd01slr:3/solr/MainSystem2>
>
> slroms1@prd02slr:slroms1/JEE/SolrProduct/logs/SolrDomain_SolrSlaveServer2/SolrSlaveServer2>
> grep "Index fetch failed" weblogic.20181018_004904.log
> 425511535 [snapPuller-14-thread-1] ERROR org.apache.solr.handler.SnapPuller
> – Master at: http://prd01slr:30000/solr/MainSystem2
> <http://prd01slr:3/solr/MainSystem2> is not available. Index fetch
> failed. Exception: Server refused connection at:
> http://prd01slr:3/solr/MainSystem2
> <http://prd01slr:3/solr/MainSystem2>
> 425511535 [snapPuller-13-thread-1] ERROR org.apache.solr.handler.SnapPuller
> – Master at: http://prd01slr:3/solr/MainSystem1
> <http://prd01slr:3/solr/MainSystem1> is not available. Index fetch
> failed. Exception: Server refused connection
> at:http://prd01slr:3/solr/MainSystem1
> <http://prd01slr:3/solr/MainSystem1>
> 598311531 [snapPuller-14-thread-1] ERROR org.apache.solr.handler.SnapPuller
> – Master at: http://prd01slr:3/solr/MainSystem2
> <http://prd01slr:3/solr/MainSystem2> is not available. Index fetch
> failed. Exception: Server refused connection
> at:http://prd01slr:3/solr/MainSystem2
> <http://prd01slr:3/solr/MainSystem2>
>
> Note –
> MainSystem1 and MainSystem2 are the Cores in our account.
> When we face this issue sometime we have to bounce our SOLR JVM’s
> and sometimes automatically it recovers and we don’t need to do any bounce.
>
> SetUp of SOLR In Account
>
> ·SOLR Version
>
>
>
> ·We are using SOLR with 1 master and 2 Slave configuration.
>
> a) Master is running with - “-Xms1G -Xmx1G -XX:MaxPermSize=256m”
> b)Slaves are running with – “-Xms8G -Xmx8G -XX:MaxPermSize=1024m”
>
> ·SOLR ear is deployed on all 3 individual Weblogic instances and it
> is same across.
> ·Indexing is getting done on Master and then we have replication +
> polling enabled on Slave JVM’s to have it in sync with Master at any time And
> all querying are being handled by SOLR Slaves only.
> ·For Polling we have defined the timing of 60 sec as highlighted
> below on Slave solr xml. (I am attaching solr xml configured to slave and
> master for your reference)
>
>
>
>
>
> ${enable.master:false}
> commit
> startup
> schema.xml,stopwords.txt
>
>
>
>
> true
> http://xx:x/solr/MainSystem2
> <http://xx:x/solr/MainSystem2>
> 00:00:60
>
>
>
>
>
> ·We have GC enabled on jvm’s too but we didn’t find anything
> suspicious there. If you need gc logs let us know.
>
> Connectivity Check
>
> ·Slave 1 –
>
>
> ·Slave 2 –
>
>
> Statistics about the Core
>
>
>
>
> Thanks and Regards
> Bharat Yadav
> Infra INT
> Amdocs Intelligent Operations, SI
> India Mob +91-987464 (WhatsApp only)
> Chile Mob +56-998022829
>
>
>
>
>
> “Amdocs’ email platform is based on a third-party, worldwide, cloud-based
> system. Any emails sent to Amdocs will be processed and stored using such
> system and are accessible by third party providers of such system on a
> limited basis. Your sending of emails to Amdocs evidences your consent to the
> use of such system and such processing, storing and access”.
>
Re: Replication Index fetch failed
rCollection.java:119) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134) at org.eclipse.jetty.server.Server.handle(Server.java:518) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572) at java.lang.Thread.run(Thread.java:745) Or should I enable more logging somewhere? FYI, the file /var/solr/data/intradesk_shard10_replica2/data/index.20160816102332501/_5qd6_ya.liv does NOT exist on the master. root@solr29-gs:~# ls /var/solr/data/intradesk_shard10_replica2/data/index.20160816102332501/ | grep 5qd6 _5qd6.fdt _5qd6.fdx _5qd6.fnm _5qd6_Lucene50_0.doc _5qd6_Lucene50_0.pos _5qd6_Lucene50_0.tim _5qd6_Lucene50_0.tip _5qd6.si _5qd6_yi.liv Thanks! Arkadi On 02-09-16 06:43, Shalin Shekhar Mangar wrote: On Thu, Sep 1, 2016 at 6:05 PM, Arkadi Colson <ark...@smartbit.be <mailto:ark...@smartbit.be>> wrote: ERROR - 2016-09-01 14:30:43.653; [c:intradesk s:shard1 r:core_node5 x:intradesk_shard1_replica1] org.apache.solr.common.SolrException; Index fetch failed :org.apache.solr.common.SolrException: Unable to download _6f46_cj.liv completely. Downloaded 0!=5596 at org.apache.solr.handler.IndexFetcher$FileFetcher.cleanup(IndexFetcher.java:1554) at org.apache.solr.handler.IndexFetcher$FileFetcher.fetchFile(IndexFetcher.java:1437) at org.apache.solr.handler.IndexFetcher.downloadIndexFiles(IndexFetcher.java:852) at org.apache.solr.handler.IndexFetcher.fetchLatestIndex(IndexFetcher.java:428) at org.apache.solr.handler.IndexFetcher.fetchLatestIndex(IndexFetcher.java:251) There should be another exception in the logs that looks like the following: "Could not download file"... That one will have a more useful stack trace. Can you please find it and paste it on email? -- Regards, Shalin Shekhar Mangar.
Re: Replication Index fetch failed
l.java:308) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246) at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572) at java.lang.Thread.run(Thread.java:745) Or should I enable more logging somewhere? FYI, the file /var/solr/data/intradesk_shard10_replica2/data/index.20160816102332501/_5qd6_ya.liv does NOT exist on the master. root@solr29-gs:~# ls /var/solr/data/intradesk_shard10_replica2/data/index.20160816102332501/ | grep 5qd6 _5qd6.fdt _5qd6.fdx _5qd6.fnm _5qd6_Lucene50_0.doc _5qd6_Lucene50_0.pos _5qd6_Lucene50_0.tim _5qd6_Lucene50_0.tip _5qd6.si _5qd6_yi.liv Thanks! Arkadi On 02-09-16 06:43, Shalin Shekhar Mangar wrote: On Thu, Sep 1, 2016 at 6:05 PM, Arkadi Colson <ark...@smartbit.be <mailto:ark...@smartbit.be>> wrote: ERROR - 2016-09-01 14:30:43.653; [c:intradesk s:shard1 r:core_node5 x:intradesk_shard1_replica1] org.apache.solr.common.SolrException; Index fetch failed :org.apache.solr.common.SolrException: Unable to download _6f46_cj.liv completely. Downloaded 0!=5596 at org.apache.solr.handler.IndexFetcher$FileFetcher.cleanup(IndexFetcher.java:1554) at org.apache.solr.handler.IndexFetcher$FileFetcher.fetchFile(IndexFetcher.java:1437) at org.apache.solr.handler.IndexFetcher.downloadIndexFiles(IndexFetcher.java:852) at org.apache.solr.handler.IndexFetcher.fetchLatestIndex(IndexFetcher.java:428) at org.apache.solr.handler.IndexFetcher.fetchLatestIndex(IndexFetcher.java:251) There should be another exception in the logs that looks like the following: "Could not download file"... That one will have a more useful stack trace. Can you please find it and paste it on email? -- Regards, Shalin Shekhar Mangar.
Re: Replication Index fetch failed
On Thu, Sep 1, 2016 at 6:05 PM, Arkadi Colson <ark...@smartbit.be> wrote: > ERROR - 2016-09-01 14:30:43.653; [c:intradesk s:shard1 r:core_node5 > x:intradesk_shard1_replica1] org.apache.solr.common.SolrException; Index > fetch failed :org.apache.solr.common.SolrException: Unable to download > _6f46_cj.liv completely. Downloaded 0!=5596 > at org.apache.solr.handler.IndexFetcher$FileFetcher.cleanup( > IndexFetcher.java:1554) > at org.apache.solr.handler.IndexFetcher$FileFetcher.fetchFile( > IndexFetcher.java:1437) > at org.apache.solr.handler.IndexFetcher.downloadIndexFiles(Inde > xFetcher.java:852) > at org.apache.solr.handler.IndexFetcher.fetchLatestIndex(IndexF > etcher.java:428) > at org.apache.solr.handler.IndexFetcher.fetchLatestIndex(IndexF > etcher.java:251) > There should be another exception in the logs that looks like the following: "Could not download file"... That one will have a more useful stack trace. Can you please find it and paste it on email? -- Regards, Shalin Shekhar Mangar.
Replication Index fetch failed
Hi
Replication seems to be in an endless loop. Anybody any idea?
See below for logs.
If you need more info, just let me know...
INFO - 2016-09-01 14:30:42.563; [c:lvs s:shard1 r:core_node10
x:lvs_shard1_replica1] org.apache.solr.core.SolrDeletionPolicy;
SolrDeletionPolicy.onCommit: commits: num=2
commit{dir=NRTCachingDirectory(MMapDirectory@/var/solr/data/lvs_shard1_replica1/data/index.20160901140036922
lockFactory=org.apache.lucene.store.NativeFSLockFactory@59509f2;
maxCacheMB=48.0 maxMergeSizeMB=4.0),segFN=segments_vpo,generation=41100}
commit{dir=NRTCachingDirectory(MMapDirectory@/var/solr/data/lvs_shard1_replica1/data/index.20160901140036922
lockFactory=org.apache.lucene.store.NativeFSLockFactory@59509f2;
maxCacheMB=48.0 maxMergeSizeMB=4.0),segFN=segments_vpp,generation=41101}
INFO - 2016-09-01 14:30:42.563; [c:lvs s:shard1 r:core_node10
x:lvs_shard1_replica1] org.apache.solr.core.SolrDeletionPolicy; newest
commit generation = 41101
INFO - 2016-09-01 14:30:42.565; [c:lvs s:shard1 r:core_node10
x:lvs_shard1_replica1] org.apache.solr.update.DirectUpdateHandler2;
end_commit_flush
INFO - 2016-09-01 14:30:42.565; [c:lvs s:shard1 r:core_node10
x:lvs_shard1_replica1] org.apache.solr.update.DirectUpdateHandler2;
start
commit{,optimize=false,openSearcher=false,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
INFO - 2016-09-01 14:30:42.603; [c:lvs s:shard1 r:core_node10
x:lvs_shard1_replica1] org.apache.solr.core.SolrDeletionPolicy;
SolrDeletionPolicy.onCommit: commits: num=2
commit{dir=NRTCachingDirectory(MMapDirectory@/var/solr/data/lvs_shard1_replica1/data/index.20160901140036922
lockFactory=org.apache.lucene.store.NativeFSLockFactory@59509f2;
maxCacheMB=48.0 maxMergeSizeMB=4.0),segFN=segments_vpp,generation=41101}
commit{dir=NRTCachingDirectory(MMapDirectory@/var/solr/data/lvs_shard1_replica1/data/index.20160901140036922
lockFactory=org.apache.lucene.store.NativeFSLockFactory@59509f2;
maxCacheMB=48.0 maxMergeSizeMB=4.0),segFN=segments_vpq,generation=41102}
INFO - 2016-09-01 14:30:42.603; [c:lvs s:shard1 r:core_node10
x:lvs_shard1_replica1] org.apache.solr.core.SolrDeletionPolicy; newest
commit generation = 41102
INFO - 2016-09-01 14:30:42.664; [c:lvs s:shard1 r:core_node10
x:lvs_shard1_replica1] org.apache.solr.search.SolrIndexSearcher; Opening
[Searcher@3436f207[lvs_shard1_replica1] realtime]
INFO - 2016-09-01 14:30:42.674; [c:lvs s:shard1 r:core_node10
x:lvs_shard1_replica1] org.apache.solr.update.DirectUpdateHandler2;
end_commit_flush
ERROR - 2016-09-01 14:30:43.653; [c:intradesk s:shard1 r:core_node5
x:intradesk_shard1_replica1] org.apache.solr.common.SolrException; Index
fetch failed :org.apache.solr.common.SolrException: Unable to download
_6f46_cj.liv completely. Downloaded 0!=5596
at
org.apache.solr.handler.IndexFetcher$FileFetcher.cleanup(IndexFetcher.java:1554)
at
org.apache.solr.handler.IndexFetcher$FileFetcher.fetchFile(IndexFetcher.java:1437)
at
org.apache.solr.handler.IndexFetcher.downloadIndexFiles(IndexFetcher.java:852)
at
org.apache.solr.handler.IndexFetcher.fetchLatestIndex(IndexFetcher.java:428)
at
org.apache.solr.handler.IndexFetcher.fetchLatestIndex(IndexFetcher.java:251)
at
org.apache.solr.handler.ReplicationHandler.doFetch(ReplicationHandler.java:388)
at
org.apache.solr.cloud.RecoveryStrategy.replicate(RecoveryStrategy.java:156)
at
org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:408)
at
org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:221)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$22(ExecutorUtil.java:229)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
ERROR - 2016-09-01 14:30:43.654; [c:intradesk s:shard1 r:core_node5
x:intradesk_shard1_replica1] org.apache.solr.common.SolrException; Error
while trying to recover:org.apache.solr.common.SolrException:
Replication for recovery failed.
at
org.apache.solr.cloud.RecoveryStrategy.replicate(RecoveryStrategy.java:159)
at
org.apache.solr.cloud.RecoveryStrategy.doRecovery(RecoveryStrategy.java:408)
at
org.apache.solr.cloud.RecoveryStrategy.run(RecoveryStrategy.java:221)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$22(ExecutorUtil.java:229)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617
Re: solr replication failing with error: Master at: is not available. Index fetch failed
hello, sorry - i overlooked this message - thanks for checking back and thanks for the info. yes - replication seems to be working now: tailed from logs just now: 2012-04-26 09:21:33,284 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-26 09:21:53,279 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-26 09:22:13,279 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-26 09:22:33,279 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. -- View this message in context: http://lucene.472066.n3.nabble.com/solr-replication-failing-with-error-Master-at-is-not-available-Index-fetch-failed-tp3932921p3941447.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: solr replication failing with error: Master at: is not available. Index fetch failed
On Apr 23, 2012, at 12:10 PM, geeky2 wrote: http://someip:someport/somepath/somecore/admin/replication/ is not available. Index fetch failed. Exception: Invalid version (expected 2, but 10) or the data in not in 'javabin' format This is kind of a bug. When Solr tries to talk in javabin and gets an http response instead (like a 404 response - what this likely is) it does this. Really it should detect this case and give you the proper error. I almost think someone made this change already in trunk based on what I was seeing yesterday, but I'm not sure. - Mark Miller lucidimagination.com
Re: solr replication failing with error: Master at: is not available. Index fetch failed
Hi, Is the replication still failing or working fine with that change ? On Tue, Apr 24, 2012 at 2:16 PM, geeky2 gee...@hotmail.com wrote: that was it! thank you. i did notice something else in the logs now ... what is the meaning or implication of the message, Connection reset.? 2012-04-24 12:59:19,996 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 12:59:39,998 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. *2012-04-24 12:59:59,997 SEVERE [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Master at: http://bogus:bogusport/somepath/somecore/replication/ is not available. Index fetch failed. Exception: Connection reset* 2012-04-24 13:00:19,998 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:00:40,004 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:00:59,992 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:01:19,993 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:01:39,992 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:01:59,989 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:02:19,990 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:02:39,989 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:02:59,991 INFO [org.a -- View this message in context: http://lucene.472066.n3.nabble.com/solr-replication-failing-with-error-Master-at-is-not-available-Index-fetch-failed-tp3932921p3936107.html Sent from the Solr - User mailing list archive at Nabble.com. -- Thanks and Regards Rahul A. Warawdekar
Re: solr replication failing with error: Master at: is not available. Index fetch failed
hello, thank you for the reply, yes - master has been indexed. ok - makes sense - the polling interval needs to change i did check the solr war file on both boxes (master and slave). they are identical. actually - if they were not indentical - this would point to a different issue altogether - since our deployment infrastructure - rolls the war file to the slaves when you do a deployment on the master. this has me stumped - not sure what to check next. -- View this message in context: http://lucene.472066.n3.nabble.com/solr-replication-failing-with-error-Master-at-is-not-available-Index-fetch-failed-tp3932921p3935699.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: solr replication failing with error: Master at: is not available. Index fetch failed
Hi, In Solr wiki, for replication, the master url is defined as follows str name=masterUrlhttp://master_host:port /solr/corename/replication/str This url does not contain admin in its path where as in the master url provided by you, you have an additional admin in the url. Not very sure if this might be an issue but you can just check removing admin and check if replication works. On Tue, Apr 24, 2012 at 11:49 AM, geeky2 gee...@hotmail.com wrote: hello, thank you for the reply, yes - master has been indexed. ok - makes sense - the polling interval needs to change i did check the solr war file on both boxes (master and slave). they are identical. actually - if they were not indentical - this would point to a different issue altogether - since our deployment infrastructure - rolls the war file to the slaves when you do a deployment on the master. this has me stumped - not sure what to check next. -- View this message in context: http://lucene.472066.n3.nabble.com/solr-replication-failing-with-error-Master-at-is-not-available-Index-fetch-failed-tp3932921p3935699.html Sent from the Solr - User mailing list archive at Nabble.com. -- Thanks and Regards Rahul A. Warawdekar
Re: solr replication failing with error: Master at: is not available. Index fetch failed
that was it! thank you. i did notice something else in the logs now ... what is the meaning or implication of the message, Connection reset.? 2012-04-24 12:59:19,996 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 12:59:39,998 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. *2012-04-24 12:59:59,997 SEVERE [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Master at: http://bogus:bogusport/somepath/somecore/replication/ is not available. Index fetch failed. Exception: Connection reset* 2012-04-24 13:00:19,998 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:00:40,004 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:00:59,992 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:01:19,993 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:01:39,992 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:01:59,989 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:02:19,990 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:02:39,989 INFO [org.apache.solr.handler.SnapPuller] (pool-12-thread-1) Slave in sync with master. 2012-04-24 13:02:59,991 INFO [org.a -- View this message in context: http://lucene.472066.n3.nabble.com/solr-replication-failing-with-error-Master-at-is-not-available-Index-fetch-failed-tp3932921p3936107.html Sent from the Solr - User mailing list archive at Nabble.com.
solr replication failing with error: Master at: is not available. Index fetch failed
hello all,
enviornment: centOS and solr 3.5
i am attempting to set up replication betweeen two solr boxes (master and
slave).
i am getting the following in the logs on the slave box.
2012-04-23 10:54:59,985 SEVERE [org.apache.solr.handler.SnapPuller]
(pool-12-thread-1) Master at:
http://someip:someport/somepath/somecore/admin/replication/ is not
available. Index fetch failed. Exception: Invalid version (expected 2, but
10) or the data in not in 'javabin' format
master jvm (jboss host) is being started like this:
-Denable.master=true
slave jvm (jboss host) is being started like this:
-Denable.slave=true
does anyone have any ideas?
i have done the following:
used curl http://someip:someport/somepath/somecore/admin/replication/ from
slave to successfully see master
used ping from slave to master
switched out the dns name for master to hard coded ip address
made sure i can see
http://someip:someport/somepath/somecore/admin/replication/ in a browser
this is my request handler - i am using the same config file on both the
master and slave - but sending in the appropriate switch on start up (per
the solr wiki page on replication)
lst name=master
str name=enable${enable.master:false}/str
str name=replicateAfterstartup/str
str name=replicateAftercommit/str
str name=confFilesschema.xml,stopwords.txt,elevate.xml/str
str name=commitReserveDuration00:00:10/str
/lst
str name=maxNumberOfBackups1/str
lst name=slave
str name=enable${enable.slave:false}/str
str
name=masterUrlhttp://someip:someport/somecore/admin/replication//str
str name=pollInterval00:00:20/str
str name=compressioninternal/str
str name=httpConnTimeout5000/str
str name=httpReadTimeout1/str
/lst
/requestHandler
any suggestions would be great
thank you,
mark
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-replication-failing-with-error-Master-at-is-not-available-Index-fetch-failed-tp3932921p3932921.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: solr replication failing with error: Master at: is not available. Index fetch failed
Hmmm, does your master have an index? In other words have you
added anything to it? I actually doubt that's an issue, but
An aside, a polling interval of 20 seconds is rather short, beware of
your autowarming time exceeding your index updates
But my _first_ guess is that somehow you're Solrs aren't the same
version or you have a foo'd index on your master.
Best
Erick
On Mon, Apr 23, 2012 at 12:10 PM, geeky2 gee...@hotmail.com wrote:
hello all,
enviornment: centOS and solr 3.5
i am attempting to set up replication betweeen two solr boxes (master and
slave).
i am getting the following in the logs on the slave box.
2012-04-23 10:54:59,985 SEVERE [org.apache.solr.handler.SnapPuller]
(pool-12-thread-1) Master at:
http://someip:someport/somepath/somecore/admin/replication/ is not
available. Index fetch failed. Exception: Invalid version (expected 2, but
10) or the data in not in 'javabin' format
master jvm (jboss host) is being started like this:
-Denable.master=true
slave jvm (jboss host) is being started like this:
-Denable.slave=true
does anyone have any ideas?
i have done the following:
used curl http://someip:someport/somepath/somecore/admin/replication/ from
slave to successfully see master
used ping from slave to master
switched out the dns name for master to hard coded ip address
made sure i can see
http://someip:someport/somepath/somecore/admin/replication/ in a browser
this is my request handler - i am using the same config file on both the
master and slave - but sending in the appropriate switch on start up (per
the solr wiki page on replication)
lst name=master
str name=enable${enable.master:false}/str
str name=replicateAfterstartup/str
str name=replicateAftercommit/str
str name=confFilesschema.xml,stopwords.txt,elevate.xml/str
str name=commitReserveDuration00:00:10/str
/lst
str name=maxNumberOfBackups1/str
lst name=slave
str name=enable${enable.slave:false}/str
str
name=masterUrlhttp://someip:someport/somecore/admin/replication//str
str name=pollInterval00:00:20/str
str name=compressioninternal/str
str name=httpConnTimeout5000/str
str name=httpReadTimeout1/str
/lst
/requestHandler
any suggestions would be great
thank you,
mark
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-replication-failing-with-error-Master-at-is-not-available-Index-fetch-failed-tp3932921p3932921.html
Sent from the Solr - User mailing list archive at Nabble.com.
Replication Error - Index fetch failed - File Not Found OverlappingFileLockException
Hi, For months, we were using apache solr 3.1.0 snapshots without problems. Recently, we have upgraded our index to apache solr 3.1.0, and also moved to a multi-core infrastructure (4 core per nodes, each core having its own index). We found that one of the index slave started to show failure, i.e., query errors. By looking at the log, we observed some errors during the latest snappull, due to two type of exceptions: - java.io.FileNotFoundException: File does not exist ... and - java.nio.channels.OverlappingFileLockException: null Then, after the failed pull, the index started to show some index related failure: java.io.IOException: read past EOF at org.apache.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java:207)] However, after manually restarting the node, everything went back to normal. You can find a more detailed log at [1]. We are afraid to see this problem occurring again. Have you some idea on what can be the cause ? Or a solution to avoid such problem ? [1] http://pastebin.com/vbnyrUgJ Thanks in advance -- Renaud Delbru
Resolved- Re: Replication Error - Index fetch failed - File Not Found OverlappingFileLockException
Hi, I found out the problem by myself. The reason was a bad deployment of of Solr on tomcat. Two instances of solr were instantiated instead of one. The two instances were managing the same indexes, and therefore were trying to write at the same time. My apologies for the noise created on the ml, -- Renaud Delbru On 30/05/11 21:52, Renaud Delbru wrote: Hi, For months, we were using apache solr 3.1.0 snapshots without problems. Recently, we have upgraded our index to apache solr 3.1.0, and also moved to a multi-core infrastructure (4 core per nodes, each core having its own index). We found that one of the index slave started to show failure, i.e., query errors. By looking at the log, we observed some errors during the latest snappull, due to two type of exceptions: - java.io.FileNotFoundException: File does not exist ... and - java.nio.channels.OverlappingFileLockException: null Then, after the failed pull, the index started to show some index related failure: java.io.IOException: read past EOF at org.apache.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java:207)] However, after manually restarting the node, everything went back to normal. You can find a more detailed log at [1]. We are afraid to see this problem occurring again. Have you some idea on what can be the cause ? Or a solution to avoid such problem ? [1] http://pastebin.com/vbnyrUgJ Thanks in advance
