Did the same FileNotFoundException / massive deletion of files occur?

Actually if you could zip them all up and post them, I'll dig through them to see if they give any clues...

Mike

Chris Harris wrote:

Ok, I did what you suggested, giving each SolrIndexWriter its own
"infoStream" log file, created in the init() method. The thing is, I
now have like 3400 infostream log files, I guess reflecting how solr
created like 3400 SolrIndexWriters over the course of the run.
(Hopefully this is plausible.) Could you explain what I should be
looking for in these files? (Posting the whole bunch of it doesn't
sound very useful.)

Thanks,
Chris

On Mon, Aug 18, 2008 at 10:12 AM, Michael McCandless
<[EMAIL PROTECTED]> wrote:

Alas, I think this won't actually turn on IndexWriter's infoStream.

I think you may need to modify the SolrIndexWriter.java sources, in the init
method, to add a call to setInfoStream(...).

Can any Solr developers confirm this?

Mike

Chris Harris wrote:

I'm assuming that one way to do this would be to set the logging level to "FINEST" in the "logging" page in the solr admin tool, and then to make sure my logging.properties file is also set to record the FINEST
logging level. Let me know if that won't enable to sort of debugging
info you are talking about. (I do understand that the logging page in the admin tool makes temporary changes that will get reverted when you
restart Solr.)

On Mon, Aug 18, 2008 at 3:05 AM, Michael McCandless
<[EMAIL PROTECTED]> wrote:

Since it seems reproducible, could you turn on debugging output
(IndexWriter.setInfoStream(...)), get the FileNotFoundException to happen
again, and post the resulting output?

Mike



Reply via email to