[SOLR-455] Better handling when index runs out of disk space

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Delivered
• Affects Version/s: 1.2, 1.3
• Component/s: update

Environment

Linux/Debian etch

• Assignee: Unassigned
• Reporter: Brian Whitman
• Created: 14/Jan/08 21:42
• Updated: 04/Oct/16 02:51
• Resolved: 04/Oct/16 02:51

Description

We had an index run out of disk space. Queries work fine but commits return
<h1>500 doc counts differ for segment _18lu: fieldsReader shows 104 but segmentInfo shows 212
org.apache.lucene.index.CorruptIndexException: doc counts differ for segment _18lu: fieldsReader shows 104 but segmentInfo shows 212
at org.apache.lucene.index.SegmentReader.initialize(SegmentReader.java:191)
I've made room, restarted resin, and now solr won't start. No useful messages in the startup, just a

[21:01:49.105] Could not start SOLR. Check solr/home property
[21:01:49.105] java.lang.NullPointerException
[21:01:49.105] at org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:100)

Solr should warn the user and/or refuse commits when the index nears the end of disk space

Issue Links

• relates to: LUCENE-1130 Hitting disk full during DocumentWriter.ThreadState.init(...) can cause hang