No OOM, no corrupted index. Just a clean instal with few documents. Similar to this: http://lucene.472066.n3.nabble.com/NoSuchFileException-errors-common-on-version-5-5-0-td4263072.html
On Wed, Nov 30, 2016 at 3:19 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 11/29/2016 8:40 AM, halis Yılboğa wrote: > > it is not normal to get that many error actually. Main problem should be > > from your index. It seems to me your index is corrupted. > > > > 29 Kas 2016 Sal, 14:40 tarihinde, Furkan KAMACI <furkankam...@gmail.com> > > şunu yazdı: > > > >> On the other hand, my Solr instance stops frequently due to such errors: > >> > >> 2016-11-29 12:25:36.962 WARN (qtp1528637575-14) [ x:collection1] > >> o.a.s.h.a.LukeRequestHandler Error getting file length for [segments_c] > >> java.nio.file.NoSuchFileException: data/index/segments_c > > If your Solr instance is actually stopping, I would suspect the OOM > script, assuming a non-windows system. On non-windows systems, recent > versions of Solr have a script that forcibly terminates Solr in the > event of an OutOfMemoryError. This script has its own log, which would > be in the same place as solr.log. > > I've never heard of Solr actually crashing on a normally configured > system, and I'm reasonably sure that the message you've indicated is not > something that would cause a crash. In fact, I've never seen it cause > any real issues, just the warning message. > > Thanks, > Shawn > >
