SOLR 7.5 : java.io.IOException
Classification: Internal Hi, I am using SOLR 7.5 master slave architecture. I am having two slaves connected to master, when load is getting increased then one my slave server CPU spikes 100% and gets terminated. In logs and monitoring I could find "java.io.IOException" coming. Please help me how to handle this problem. Regards, Akreeti Agarwal ::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.
SOLR PERFORMANCE Warning
Hi All, I am using SOLR 7.5 version with master slave architecture. I am getting : "PERFORMANCE WARNING: Overlapping onDeckSearchers=2" continuously on my master logs for all cores. Please help me to resolve this. Thanks & Regards, Akreeti Agarwal ::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.
SOLR 7.5 Performance WARN
Hi All, I am using SOLR 7.5 version with master slave architecture. I am getting : "PERFORMANCE WARNING: Overlapping onDeckSearchers=2" continuously on my master logs for all cores. Please help me to resolve this. Thanks & Regards, Akreeti Agarwal ::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.
Issue on solr master
Hi All, I am just setting up my solr master. I am using solr-7.5.0 version with master slave architecture. On my master server, I have started the jetty server using: ./solr start -p 8983 After starting the server, I am continuously getting this error in my master server logs: org.apache.solr.common.SolrException: Solr instance is not running in SolrCloud mode Solr has started dashboard has opened, but I am getting this error in logs. Please help Thanks & Regards, Akreeti Agarwal ::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.
no files to download for index generation
Hi All, I am getting error No files to download for index generation: 1385219 continuously on my slave servers. I am using solr-5.5.5 with one master and two slave architecture. Please help me on this. Does this error impacts replication also or performance issue on data query?? 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.
Exceptions in solr log
Hi All, Please help me with these exceptions and their workarounds: 1. org.apache.solr.common.SolrException: org.apache.solr.search.SyntaxError: Cannot parse 2. o.a.s.h.IndexFetcher No files to download for index generation: 1394327 3. o.a.s.h.a.LukeRequestHandler Error getting file length for [segments_b] (this one is warning as discussed) I am getting these errors always in my solr logs, what can be the reason behind them and how should I resolve it. Thanks & Regards, Akreeti Agarwal ::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: Solr master issue : IndexNotFoundException
Hi, I removed the write.lock file from the index and then restarted the solr server, but still the same issue was observed. Thanks & Regards, Akreeti Agarwal (M) +91-8318686601 -Original Message- From: Atita Arora Sent: Wednesday, November 27, 2019 7:21 PM To: solr-user@lucene.apache.org Subject: Re: Solr master issue : IndexNotFoundException It seems to be either the permission problem or maybe because of the write.lock file not removed due to process kill. Did you happen to check this one ? https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flucene.472066.n3.nabble.com%2FSolrCore-collection1-is-not-available-due-to-init-failure-td4094869.htmldata=02%7C01%7CAkreetiA%40hcl.com%7Cdcd1c099bccf4ed715d808d77340ed96%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637104595013784239sdata=SGjPkO92vio%2Ff8c5FqinQleRkz4nfor9fRcC5FEw3Ss%3Dreserved=0 On Wed, Nov 27, 2019 at 2:28 PM Akreeti Agarwal wrote: > Hi All, > > I am getting these two errors after restarting my solr master server: > > null:org.apache.solr.common.SolrException: SolrCore 'sitecore_web_index' > is not available due to init failure: Error opening new searcher > > Caused by: org.apache.lucene.index.IndexNotFoundException: no > segments* file found in > LockValidatingDirectoryWrapper(NRTCachingDirectory(MMapDirectory@/solr > -m/server/solr/sitecore_web_index/data/index > lockFactory=org.apache.lucene.store.NativeFSLockFactory@5c6c24fd; > maxCacheMB=48.0 maxMergeSizeMB=4.0)) > > Please help to resolve this. > > 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. > >
Solr master issue : IndexNotFoundException
Hi All, I am getting these two errors after restarting my solr master server: null:org.apache.solr.common.SolrException: SolrCore 'sitecore_web_index' is not available due to init failure: Error opening new searcher Caused by: org.apache.lucene.index.IndexNotFoundException: no segments* file found in LockValidatingDirectoryWrapper(NRTCachingDirectory(MMapDirectory@/solr-m/server/solr/sitecore_web_index/data/index lockFactory=org.apache.lucene.store.NativeFSLockFactory@5c6c24fd; maxCacheMB=48.0 maxMergeSizeMB=4.0)) Please help to resolve this. 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: Replication Iteration
Hi, I have no idea about how much time is taken for successful replication for 2.62 GB. How much should I set "commitReserveDuration" for 2.62 GB ? Thanks & Regards, Akreeti Agarwal -Original Message- From: Paras Lehana Sent: Thursday, September 12, 2019 6:46 PM To: solr-user@lucene.apache.org Subject: Re: Replication Iteration Hey Akreeti, 00:00:10 Have you tried increasing *commitReserveDuration*? Do you have any idea how much time your successful replications take for 2.62 GB? On Wed, 11 Sep 2019 at 22:30, Akreeti Agarwal wrote: > Hi, > > It fails many times, sharing the iteration: > > Passed: > Wed Sep 11 16:49:18 UTC 2019 > Wed Sep 11 16:48:56 UTC 2019 > Wed Sep 11 16:48:36 UTC 2019 > Wed Sep 11 16:48:18 UTC 2019 > Wed Sep 11 16:47:55 UTC 2019 > Wed Sep 11 16:47:35 UTC 2019 > Wed Sep 11 16:47:16 UTC 2019 > Wed Sep 11 16:46:55 UTC 2019 > Wed Sep 11 16:46:33 UTC 2019 > > Failed: > Wed Sep 11 16:42:47 UTC 2019 > Wed Sep 11 16:36:07 UTC 2019 > Wed Sep 11 16:32:47 UTC 2019 > Wed Sep 11 16:29:27 UTC 2019 > Wed Sep 11 16:24:27 UTC 2019 > Wed Sep 11 16:11:07 UTC 2019 > Wed Sep 11 16:09:47 UTC 2019 > Wed Sep 11 16:05:47 UTC 2019 > Wed Sep 11 15:53:27 UTC 2019 > Wed Sep 11 15:51:47 UTC 2019 > > Memory details: > > total used free sharedbuffers cached > Mem: 15947 15549398 62198 5650 > -/+ buffers/cache: 9700 6246 > Swap:0 0 0 > > > Thanks & Regards, > Akreeti Agarwal > > > -Original Message- > From: Jon Kjær Amundsen > Sent: Wednesday, September 11, 2019 7:28 PM > To: solr-user@lucene.apache.org > Subject: Re: Replication Iteration > > Is it every time it fails, or just sometimes? > What is the timestamps on the failed and passed iterations? > And how much disk space do you have available on the slave? > > Venlig hilsen/Best regards > > *Jon Kjær Amundsen* > Developer > > > Phone: +45 7023 9080 > E-mail: j...@udbudsvagten.dk > Web: > https://apc01.safelinks.protection.outlook.com/?url=www.udbudsvagten.d > kdata=02%7C01%7CAkreetiA%40hcl.com%7Cf7230fabcabe4144303c08d73783 > 6ad1%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038909894888022 > mp;sdata=jABLGHXUJv6DyJ6vqiHRHgr0PbiP8Si2gMDD5fMxDls%3Dreserved=0 > Parken - Tårn D - 5. Sal > Øster Allé 48 | DK - 2100 København > > < > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdk.li > nkedin.com%2Fin%2FJonKjaerAmundsen%2Fdata=02%7C01%7CAkreetiA%40hc > l.com%7Cf7230fabcabe4144303c08d737836ad1%7C189de737c93a4f5a8b686f4ca99 > 41912%7C0%7C0%7C637038909894888022sdata=UTMNsDYtN2OiLfkItVP6JwE3V > WSPhhWHvCGBIZfLifU%3Dreserved=0 > > > > Intelligent Offentlig Samhandel > *Før, under og efter udbud* > > *Følg UdbudsVagten og markedet her Linkedin < > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.l > inkedin.com%2Fgroups%3FgroupDashboard%3D%26gid%3D1862353data=02%7 > C01%7CAkreetiA%40hcl.com%7Cf7230fabcabe4144303c08d737836ad1%7C189de737 > c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038909894888022sdata=tI2RNk > nFQjpFZZHaIM7gedcVdwEs6uJGgQH7FEHX5ag%3Dreserved=0> > * > > > Den ons. 11. sep. 2019 kl. 15.23 skrev Akreeti Agarwal : > > > My index size is 2.62 GB, and : > > 00:00:10 > > > > Thanks & Regards, > > Akreeti Agarwal > > > > > > -Original Message- > > From: Paras Lehana > > Sent: Wednesday, September 11, 2019 5:39 PM > > To: solr-user@lucene.apache.org > > Subject: Re: Replication Iteration > > > > What is the size of your index? Is it too big? How fast is your link > > between master and slave? > > > > I'm asking these because, for larger indexes, you may want to raise > > commitReserveDuration defined in ReplicationHandler in solrconfig.xml. > > > > 00:00:10 > > > > > > From SolrReplication > > < > > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcw > > ik > > i.apache.org%2Fconfluence%2Fdisplay%2Fsolr%2FSolrReplicationdat > > a= > > 02%7C01%7CAkreetiA%40hcl.com%7Cd0ccab4b71554c325d0e08d736c019bb%7C18 > > 9d > > e737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038071020061996sdata= > > 4p > > rY6X8%2FXVTbFj9OAlgQ1t6Vq7GFytRPHNzPsQkFktc%3Dreserved=0 > > > > > documentation for Master > > < > > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcw > > ik > > i.apache.org%2Fconfluence%2Fdisplay%2Fsolr%2FSolrReplication%23Maste > > r& > > amp;data=02%7C01%7CAkreetiA%40hcl.com%7Cd0ccab4b71554c325d0e
RE: Replication Iteration
Hi, It fails many times, sharing the iteration: Passed: Wed Sep 11 16:49:18 UTC 2019 Wed Sep 11 16:48:56 UTC 2019 Wed Sep 11 16:48:36 UTC 2019 Wed Sep 11 16:48:18 UTC 2019 Wed Sep 11 16:47:55 UTC 2019 Wed Sep 11 16:47:35 UTC 2019 Wed Sep 11 16:47:16 UTC 2019 Wed Sep 11 16:46:55 UTC 2019 Wed Sep 11 16:46:33 UTC 2019 Failed: Wed Sep 11 16:42:47 UTC 2019 Wed Sep 11 16:36:07 UTC 2019 Wed Sep 11 16:32:47 UTC 2019 Wed Sep 11 16:29:27 UTC 2019 Wed Sep 11 16:24:27 UTC 2019 Wed Sep 11 16:11:07 UTC 2019 Wed Sep 11 16:09:47 UTC 2019 Wed Sep 11 16:05:47 UTC 2019 Wed Sep 11 15:53:27 UTC 2019 Wed Sep 11 15:51:47 UTC 2019 Memory details: total used free sharedbuffers cached Mem: 15947 15549398 62198 5650 -/+ buffers/cache: 9700 6246 Swap:0 0 0 Thanks & Regards, Akreeti Agarwal -Original Message- From: Jon Kjær Amundsen Sent: Wednesday, September 11, 2019 7:28 PM To: solr-user@lucene.apache.org Subject: Re: Replication Iteration Is it every time it fails, or just sometimes? What is the timestamps on the failed and passed iterations? And how much disk space do you have available on the slave? Venlig hilsen/Best regards *Jon Kjær Amundsen* Developer Phone: +45 7023 9080 E-mail: j...@udbudsvagten.dk Web: https://apc01.safelinks.protection.outlook.com/?url=www.udbudsvagten.dkdata=02%7C01%7CAkreetiA%40hcl.com%7Cd0ccab4b71554c325d0e08d736c019bb%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038071020061996sdata=DSWnCimBzOilM8DoS4efsbgE%2BP%2BG2RDP0IUjolch7Z4%3Dreserved=0 Parken - Tårn D - 5. Sal Øster Allé 48 | DK - 2100 København <https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdk.linkedin.com%2Fin%2FJonKjaerAmundsen%2Fdata=02%7C01%7CAkreetiA%40hcl.com%7Cd0ccab4b71554c325d0e08d736c019bb%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038071020061996sdata=84xwmZ%2BEj6u9sXiSmM7QMKHpkDMpYMpltFNhKT6v7F0%3Dreserved=0> Intelligent Offentlig Samhandel *Før, under og efter udbud* *Følg UdbudsVagten og markedet her Linkedin <https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fgroups%3FgroupDashboard%3D%26gid%3D1862353data=02%7C01%7CAkreetiA%40hcl.com%7Cd0ccab4b71554c325d0e08d736c019bb%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038071020061996sdata=pFZ%2FUDSmCzzuUJur74FMF9%2FDXSCKkJHCs8x4Wj3Jyfo%3Dreserved=0> * Den ons. 11. sep. 2019 kl. 15.23 skrev Akreeti Agarwal : > My index size is 2.62 GB, and : > 00:00:10 > > Thanks & Regards, > Akreeti Agarwal > > > -Original Message- > From: Paras Lehana > Sent: Wednesday, September 11, 2019 5:39 PM > To: solr-user@lucene.apache.org > Subject: Re: Replication Iteration > > What is the size of your index? Is it too big? How fast is your link > between master and slave? > > I'm asking these because, for larger indexes, you may want to raise > commitReserveDuration defined in ReplicationHandler in solrconfig.xml. > > 00:00:10 > > > From SolrReplication > < > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwik > i.apache.org%2Fconfluence%2Fdisplay%2Fsolr%2FSolrReplicationdata= > 02%7C01%7CAkreetiA%40hcl.com%7Cd0ccab4b71554c325d0e08d736c019bb%7C189d > e737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038071020061996sdata=4p > rY6X8%2FXVTbFj9OAlgQ1t6Vq7GFytRPHNzPsQkFktc%3Dreserved=0 > > > documentation for Master > < > https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwik > i.apache.org%2Fconfluence%2Fdisplay%2Fsolr%2FSolrReplication%23Master& > amp;data=02%7C01%7CAkreetiA%40hcl.com%7Cd0ccab4b71554c325d0e08d736c019 > bb%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038071020061996 > ;sdata=vPlsIvqTrwzq0wSkBkMiJc3C7IOaXpQWdwG06xRlG9k%3Dreserved=0 > >: > > If your commits are very frequent and network is particularly slow, > you can > > tweak an extra attribute name="commitReserveDuration">00:00:10. > > This is roughly the time taken to download 5MB from master to slave. > > Default is 10 secs. > > > Do check the hyperlinks. > > On Wed, 11 Sep 2019 at 17:25, Akreeti Agarwal wrote: > > > I am seeing the logs on both UI and file, but I only see this error: > > > > ReplicationHandler > > Index fetch failed :org.apache.solr.common.SolrException: Unable to > > download segments_znow completely. Downloaded 0!=2217 > > > > Thanks & Regards, > > Akreeti Agarwal > > > > -Original Message- > > From: Paras Lehana > > Sent: Wednesday, September 11, 2019 5:17 PM > > To: solr-user@lucene.apache.org > > Subject: Re: Replication Iteration > > > > Hi Akreeti, > > > > Have you tried using the old UI to see errors? I had always > >
RE: Replication Iteration
My index size is 2.62 GB, and : 00:00:10 Thanks & Regards, Akreeti Agarwal -Original Message- From: Paras Lehana Sent: Wednesday, September 11, 2019 5:39 PM To: solr-user@lucene.apache.org Subject: Re: Replication Iteration What is the size of your index? Is it too big? How fast is your link between master and slave? I'm asking these because, for larger indexes, you may want to raise commitReserveDuration defined in ReplicationHandler in solrconfig.xml. 00:00:10 From SolrReplication <https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2Fsolr%2FSolrReplicationdata=02%7C01%7CAkreetiA%40hcl.com%7C23769a9cc4094154170008d736b0f190%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038005907686643sdata=NEwvmMCXOFB7v56IuNJ8cJglInSJZjLTSUQTT6d07f0%3Dreserved=0> documentation for Master <https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2Fsolr%2FSolrReplication%23Masterdata=02%7C01%7CAkreetiA%40hcl.com%7C23769a9cc4094154170008d736b0f190%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637038005907686643sdata=5gX%2FbeaPUQWxMkJ8bD4Jt%2BB7feB509VHD25d66iLCnU%3Dreserved=0>: If your commits are very frequent and network is particularly slow, you can > tweak an extra attribute 00:00:10. > This is roughly the time taken to download 5MB from master to slave. > Default is 10 secs. Do check the hyperlinks. On Wed, 11 Sep 2019 at 17:25, Akreeti Agarwal wrote: > I am seeing the logs on both UI and file, but I only see this error: > > ReplicationHandler > Index fetch failed :org.apache.solr.common.SolrException: Unable to > download segments_znow completely. Downloaded 0!=2217 > > Thanks & Regards, > Akreeti Agarwal > > -Original Message- > From: Paras Lehana > Sent: Wednesday, September 11, 2019 5:17 PM > To: solr-user@lucene.apache.org > Subject: Re: Replication Iteration > > Hi Akreeti, > > Have you tried using the old UI to see errors? I had always > experienced not seeing status updates about replication in the newer > UI. Check for the option on top right of Solr UI. > > And where are you seeing logs - on solr UI or from a file? > > On Wed, 11 Sep 2019 at 16:12, Akreeti Agarwal wrote: > > > In the logs I don't see any errors, mostly after every 1-2 min > > replication fails and I am not able to identify the root cause for it. > > > > Thanks & Regards, > > Akreeti Agarwal > > > > -Original Message- > > From: Jon Kjær Amundsen > > Sent: Wednesday, September 11, 2019 12:15 PM > > To: solr-user@lucene.apache.org > > Subject: Re: Replication Iteration > > > > It depends on the timestamps. > > The red iterations are failed replications and the green are passed > > replications. > > If the newest timestamp is green the latest replication went well, > > if it is red, it failed. > > > > You should check the solr log on the slave if a recent replication > > have failed to see the cause. > > > > Venlig hilsen/Best regards > > > > *Jon Kjær Amundsen* > > Developer > > > > > > Phone: +45 7023 9080 > > E-mail: j...@udbudsvagten.dk > > Web: > > https://apc01.safelinks.protection.outlook.com/?url=www.udbudsvagten > > .d > > kdata=02%7C01%7CAkreetiA%40hcl.com%7Cdac98a88d43446d88f8208d736 > > ad > > ebfa%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037992931651416 > > > > mp;sdata=HBrEXexrQZ2UrhmDwGaZfnvn4XjbawVGq8PnMDA5ocA%3Dreserved > > =0 > > Parken - Tårn D - 5. Sal > > Øster Allé 48 | DK - 2100 København > > > > < > > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdk. > > li > > nkedin.com%2Fin%2FJonKjaerAmundsen%2Fdata=02%7C01%7CAkreetiA%40 > > hc > > l.com%7Cdac98a88d43446d88f8208d736adebfa%7C189de737c93a4f5a8b686f4ca > > 99 > > 41912%7C0%7C1%7C637037992931651416sdata=9sealYl8sRN7Et2Oc%2F8Nx > > nx > > ooisjC15hPV5y9NSCgKg%3Dreserved=0 > > > > > > > Intelligent Offentlig Samhandel > > *Før, under og efter udbud* > > > > *Følg UdbudsVagten og markedet her Linkedin < > > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww > > .l > > inkedin.com%2Fgroups%3FgroupDashboard%3D%26gid%3D1862353data=02 > > %7 > > C01%7CAkreetiA%40hcl.com%7Cdac98a88d43446d88f8208d736adebfa%7C189de7 > > 37 > > c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037992931651416sdata=zQVT > > %2 FJjMY6GlU4IVHZEMc6P4EWh9MrMcWEybBonKn7w%3Dreserved=0> > > * > > > > > > Den ons. 11. sep. 2019 kl. 06.35 skrev Akreeti Agarwal > > >: > > >
RE: Replication Iteration
I am seeing the logs on both UI and file, but I only see this error: ReplicationHandler Index fetch failed :org.apache.solr.common.SolrException: Unable to download segments_znow completely. Downloaded 0!=2217 Thanks & Regards, Akreeti Agarwal -Original Message- From: Paras Lehana Sent: Wednesday, September 11, 2019 5:17 PM To: solr-user@lucene.apache.org Subject: Re: Replication Iteration Hi Akreeti, Have you tried using the old UI to see errors? I had always experienced not seeing status updates about replication in the newer UI. Check for the option on top right of Solr UI. And where are you seeing logs - on solr UI or from a file? On Wed, 11 Sep 2019 at 16:12, Akreeti Agarwal wrote: > In the logs I don't see any errors, mostly after every 1-2 min > replication fails and I am not able to identify the root cause for it. > > Thanks & Regards, > Akreeti Agarwal > > -Original Message- > From: Jon Kjær Amundsen > Sent: Wednesday, September 11, 2019 12:15 PM > To: solr-user@lucene.apache.org > Subject: Re: Replication Iteration > > It depends on the timestamps. > The red iterations are failed replications and the green are passed > replications. > If the newest timestamp is green the latest replication went well, if > it is red, it failed. > > You should check the solr log on the slave if a recent replication > have failed to see the cause. > > Venlig hilsen/Best regards > > *Jon Kjær Amundsen* > Developer > > > Phone: +45 7023 9080 > E-mail: j...@udbudsvagten.dk > Web: > https://apc01.safelinks.protection.outlook.com/?url=www.udbudsvagten.d > kdata=02%7C01%7CAkreetiA%40hcl.com%7Cdac98a88d43446d88f8208d736ad > ebfa%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037992931651416 > mp;sdata=HBrEXexrQZ2UrhmDwGaZfnvn4XjbawVGq8PnMDA5ocA%3Dreserved=0 > Parken - Tårn D - 5. Sal > Øster Allé 48 | DK - 2100 København > > < > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdk.li > nkedin.com%2Fin%2FJonKjaerAmundsen%2Fdata=02%7C01%7CAkreetiA%40hc > l.com%7Cdac98a88d43446d88f8208d736adebfa%7C189de737c93a4f5a8b686f4ca99 > 41912%7C0%7C1%7C637037992931651416sdata=9sealYl8sRN7Et2Oc%2F8Nxnx > ooisjC15hPV5y9NSCgKg%3Dreserved=0 > > > > Intelligent Offentlig Samhandel > *Før, under og efter udbud* > > *Følg UdbudsVagten og markedet her Linkedin < > https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.l > inkedin.com%2Fgroups%3FgroupDashboard%3D%26gid%3D1862353data=02%7 > C01%7CAkreetiA%40hcl.com%7Cdac98a88d43446d88f8208d736adebfa%7C189de737 > c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037992931651416sdata=zQVT%2 > FJjMY6GlU4IVHZEMc6P4EWh9MrMcWEybBonKn7w%3Dreserved=0> > * > > > Den ons. 11. sep. 2019 kl. 06.35 skrev Akreeti Agarwal : > > > Hi All, > > > > I am using solr-5.5.5, in which I have one master and two slaves. I > > see some red and some green replication iteration on my slave side. > > What does these red and green iteration means? > > Will this cause problem? > > > > Thanks & Regards, > > Akreeti Agarwal > > > > ::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. > > > > > -- -- Regards, *Paras Lehana* [65871] Software Programmer, Auto-Suggest, IndiaMART Intermesh Ltd. 8th Floor, Tower A, Advant-Navis Business Park, Sector 142, Noida, UP, IN - 201303 Mob.: +91-9560911996 Work: 01203916600 | Extn: *8173* -- IMPORTANT: NEVER share your IndiaMART OTP/ Password with anyone.
RE: Replication Iteration
In the logs I don't see any errors, mostly after every 1-2 min replication fails and I am not able to identify the root cause for it. Thanks & Regards, Akreeti Agarwal -Original Message- From: Jon Kjær Amundsen Sent: Wednesday, September 11, 2019 12:15 PM To: solr-user@lucene.apache.org Subject: Re: Replication Iteration It depends on the timestamps. The red iterations are failed replications and the green are passed replications. If the newest timestamp is green the latest replication went well, if it is red, it failed. You should check the solr log on the slave if a recent replication have failed to see the cause. Venlig hilsen/Best regards *Jon Kjær Amundsen* Developer Phone: +45 7023 9080 E-mail: j...@udbudsvagten.dk Web: https://apc01.safelinks.protection.outlook.com/?url=www.udbudsvagten.dkdata=02%7C01%7CAkreetiA%40hcl.com%7Ccede491a1aa34fddc7cc08d73683a389%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037811343910361sdata=4GyE5bBQdOoIZW3GH5uB%2FmA1jqzsQqBmJmvg3U6PDsg%3Dreserved=0 Parken - Tårn D - 5. Sal Øster Allé 48 | DK - 2100 København <https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdk.linkedin.com%2Fin%2FJonKjaerAmundsen%2Fdata=02%7C01%7CAkreetiA%40hcl.com%7Ccede491a1aa34fddc7cc08d73683a389%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037811343910361sdata=YsXMQqLqxXvwoF3d1Juq9LB60gNT9%2FQSVD3L8y08a%2B4%3Dreserved=0> Intelligent Offentlig Samhandel *Før, under og efter udbud* *Følg UdbudsVagten og markedet her Linkedin <https://apc01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fgroups%3FgroupDashboard%3D%26gid%3D1862353data=02%7C01%7CAkreetiA%40hcl.com%7Ccede491a1aa34fddc7cc08d73683a389%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637037811343910361sdata=Eibo4cubbi%2BTkukH6D9SClTafKzB5Xud2EnJBX9xD0Q%3Dreserved=0> * Den ons. 11. sep. 2019 kl. 06.35 skrev Akreeti Agarwal : > Hi All, > > I am using solr-5.5.5, in which I have one master and two slaves. I > see some red and some green replication iteration on my slave side. > What does these red and green iteration means? > Will this cause problem? > > Thanks & Regards, > Akreeti Agarwal > > ::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. > >
Replication Iteration
Hi All, I am using solr-5.5.5, in which I have one master and two slaves. I see some red and some green replication iteration on my slave side. What does these red and green iteration means? Will this cause problem? Thanks & Regards, Akreeti Agarwal ::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
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
Solr Master Issue
) at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:362) at org.apache.lucene.index.IndexFileDeleter.(IndexFileDeleter.java:171) at org.apache.lucene.index.IndexWriter.(IndexWriter.java:949) at org.apache.solr.update.SolrIndexWriter.(SolrIndexWriter.java:78) at org.apache.solr.update.SolrIndexWriter.create(SolrIndexWriter.java:65) at org.apache.solr.update.DefaultSolrCoreState.createMainIndexWriter(DefaultSolrCoreState.java:237) at org.apache.solr.update.DefaultSolrCoreState.getIndexWriter(DefaultSolrCoreState.java:111) at org.apache.solr.core.SolrCore.openNewSearcher(SolrCore.java:1657) ... 13 more 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
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
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. > > -- > >
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: Solr master issue
SOLR version is : solr-5.5.5 Thanks & Regards, Akreeti Agarwal -Original Message- From: Akreeti Agarwal Sent: Wednesday, August 21, 2019 5:47 PM To: solr-user@lucene.apache.org Subject: Solr master issue Hi, I am facing issue on my solr master, getting this in logs: 2019-08-19 22:29:55.573 ERROR (qtp59559151-101) [ ] o.a.s.s.HttpSolrCall null:org.apache.solr.common.SolrException: SolrCore 'sitecore_contents_index' is not available due to init failure: Error opening new searcher at org.apache.solr.core.CoreContainer.getCore(CoreContainer.java:1071) at org.apache.solr.servlet.HttpSolrCall.init(HttpSolrCall.java:252) at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:414) 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) Caused by: org.apache.solr.common.SolrException: Error opening new searcher at org.apache.solr.core.SolrCore.(SolrCore.java:820) at org.apache.solr.core.SolrCore.(SolrCore.java:658) at org.apache.solr.core.CoreContainer.create(CoreContainer.java:820) at org.apache.solr.core.CoreContainer.access$000(CoreContainer.java:90) at org.apache.solr.core.CoreContainer$1.call(CoreContainer.java:473) at org.apache.solr.core.CoreContainer$1.call(CoreContainer.java:464) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor$1.run(ExecutorUtil.java:231) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ... 1 more Caused by: org.apache.solr.common.SolrException: Error opening new searcher at org.apache.solr.core.SolrCore.openNewSearcher(SolrCore.java:1696) at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:1807) at org.apache.solr.core.SolrCore.initSearcher(SolrCore.java:914) at org.apache.solr.core.SolrCore.(SolrCore.java:793) ... 10 more Caused by: java.nio.file.NoSuchFileException: /solr-m/server/solr/sitecore_contents_index_rebuild/data/index/_6lps.si 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.UnixFileSystemProvider.newFileChannel(UnixFileSystemProvider.java:177) at java.nio.channels.FileChannel.open(FileChannel.java:287) at java.nio.channels.FileChannel.open(FileChannel.java
Solr master issue
(Directory.java:109) at org.apache.lucene.codecs.lucene50.Lucene50SegmentInfoFormat.read(Lucene50SegmentInfoFormat.java:82) at org.apache.lucene.index.SegmentInfos.readCommit(SegmentInfos.java:362) at org.apache.lucene.index.IndexFileDeleter.(IndexFileDeleter.java:171) at org.apache.lucene.index.IndexWriter.(IndexWriter.java:949) at org.apache.solr.update.SolrIndexWriter.(SolrIndexWriter.java:78) at org.apache.solr.update.SolrIndexWriter.create(SolrIndexWriter.java:65) at org.apache.solr.update.DefaultSolrCoreState.createMainIndexWriter(DefaultSolrCoreState.java:237) at org.apache.solr.update.DefaultSolrCoreState.getIndexWriter(DefaultSolrCoreState.java:111) at org.apache.solr.core.SolrCore.openNewSearcher(SolrCore.java:1657) ... 13 more Please help to resolve this issue. 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. --
