[
https://issues.apache.org/jira/browse/SOLR-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559161#action_12559161
]
Otis Gospodnetic commented on SOLR-455:
---------------------------------------
My guess would be that this is really out of scope for Solr and should be (is
in 2.3!) done on the Lucene level.
As for Java being able to get info about disk usage, I believe Java 7 will have
that.
> Better handling when index runs out of disk space
> -------------------------------------------------
>
> Key: SOLR-455
> URL: https://issues.apache.org/jira/browse/SOLR-455
> Project: Solr
> Issue Type: Bug
> Components: update
> Affects Versions: 1.2, 1.3
> Environment: Linux/Debian etch
> Reporter: Brian Whitman
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
