Indexer silently dies when FSDirectory cannot be created about couchdb-lucene

[rnewson]

Ah, good catch. I'll improve the handling here.

[rnewson]

If the main() method exists, couch will still complain.

Is the purpose of your patch to get better error output? It doesn't appear that it will stop couch restarting the external over and over, and the exception above is much more useful (to me) that a log message.

[hntrmrrs]

I agree. To fully solve the problem, I expect that Couch will need to pay more attention to why the process died. I think the log message is useful when first configuring Lucene because new users who aren't familiar with Java will struggle to pinpoint why it's failing to start with a bad couchdb.lucene.dir configuration option.

In the meantime, I'll look at possible ways of notifying Couch that the process won't start and thus shouldn't be continually restarted.

[rnewson]

right. I'm shoring up error handling right now so I'll add your check (or equivalent).

I can arrange for a non-zero exit code in the event of these errors, if that would help with the couch modifications?

[rnewson]

Ok, for now, I test for a few conditions and log a clearer error message if the directory isn't writable (with the absolute path for clarity).

If couch provides a more nuanced interaction for this kind of error handling, I'll gladly enhance further.