Re: IndexFetcher cannot download index file

2018-04-24 Thread Shawn Heisey
On 4/24/2018 1:53 PM, Markus Jelsma wrote: > I don't see stack traces for most WARNs, for example the checksum > warning on recovery (other thread), or the Trie* deprecations. I just tried it on 7.3.0.  Added a line to CoreContainer.java to log an exception at warn when Solr is starting:     log

RE: IndexFetcher cannot download index file

2018-04-24 Thread Markus Jelsma
Inline. -Original message- > From:Shawn Heisey > Sent: Tuesday 24th April 2018 21:18 > To: solr-user@lucene.apache.org > Subject: Re: IndexFetcher cannot download index file > > On 4/24/2018 12:36 PM, Markus Jelsma wrote: > > I should be more precise, i said the

Re: IndexFetcher cannot download index file

2018-04-24 Thread Shawn Heisey
On 4/24/2018 12:36 PM, Markus Jelsma wrote: > I should be more precise, i said the stack traces of WARN are not shown, only > the messages are visible. The 'low disk space' line was hidden in the stack > trace of the WARN, as you can see in the pasted example, thus invisible in > the GUI with de

RE: IndexFetcher cannot download index file

2018-04-24 Thread Markus Jelsma
l never recover and in > the mean time not show why the recovery failed. > > What do you think? > > Regards, > Markus > > > > -Original message- > > From:Shawn Heisey > > Sent: Tuesday 24th April 2018 19:12 > > To: solr-user@lucene.apach

RE: IndexFetcher cannot download index file

2018-04-24 Thread Markus Jelsma
ds, Markus -Original message- > From:Shawn Heisey > Sent: Tuesday 24th April 2018 19:12 > To: solr-user@lucene.apache.org > Subject: Re: IndexFetcher cannot download index file > > On 4/24/2018 9:46 AM, Markus Jelsma wrote: > > Disk space was WARN level. It seem

Re: IndexFetcher cannot download index file

2018-04-24 Thread Shawn Heisey
On 4/24/2018 9:46 AM, Markus Jelsma wrote: > Disk space was WARN level. It seems only stack traces of ERROR level messages > are visible via the GUI, and that is where the 'No space left' was hiding. > Without logging in and inspecting the logs manually, you will never notice > that message. Th

Re: IndexFetcher cannot download index file

2018-04-24 Thread Charlie Hull
On 24/04/2018 16:44, Walter Underwood wrote: In Ultraseek, we checked free disk space before starting a merge or replication. If there wasn’t enough space, it emailed an error to the admin and disabled merging or replication, respectively. Checking free disk space on Windows was a pain. On a

RE: IndexFetcher cannot download index file

2018-04-24 Thread Markus Jelsma
> To: solr-user@lucene.apache.org > Subject: Re: IndexFetcher cannot download index file > > On 4/24/2018 6:52 AM, Markus Jelsma wrote: > > Forget about it, recovery got a java.io.IOException: No space left on > > device but it wasn't clear until i inspected the real logs. >

Re: IndexFetcher cannot download index file

2018-04-24 Thread Walter Underwood
In Ultraseek, we checked free disk space before starting a merge or replication. If there wasn’t enough space, it emailed an error to the admin and disabled merging or replication, respectively. Checking free disk space on Windows was a pain. wunder Walter Underwood wun...@wunderwood.org http:/

Re: IndexFetcher cannot download index file

2018-04-24 Thread Shawn Heisey
On 4/24/2018 6:52 AM, Markus Jelsma wrote: Forget about it, recovery got a java.io.IOException: No space left on device but it wasn't clear until i inspected the real logs. The logs in de web admin didn't show the disk space exception, even when i expand the log line. Maybe that could be chang

RE: IndexFetcher cannot download index file

2018-04-24 Thread Markus Jelsma
Forget about it, recovery got a java.io.IOException: No space left on device but it wasn't clear until i inspected the real logs. The logs in de web admin didn't show the disk space exception, even when i expand the log line. Maybe that could be changed. Thanks, Markus -Original messag