So, I tried 'optimize', but it failed because of lack of space on the first machine. I then moved the whole thing to a different machine where the index was pretty much the only thing and was using about 37% of disk, but it still failed because of a "No space left on device" IOException. Also, the size of the index has since doubled to roughly 74% of the disk on this second machine now and the number of files has increased from 3289 to 3329. Actually even the 3289 files on the first machine were after I tried optimize on it once, so the "original" size must have been even smaller.
I don't think I can afford any more space and am close to giving up and reclaiming space on the two machines. A couple more questions before that: 1) I am tempted to try editing binary--the "magnetic needle" option. Could you elaborate on this? Would there be a way to go back to an index that is the original size from its super-sized current form(s)? 2) Will CheckIndex also need more than twice the space? Would there be a way to bring down the size to the original size without running 'optimize' if I try that route? Also how exactly do I run CheckIndex, e.g., the exact URL I need to hit? -- View this message in context: http://lucene.472066.n3.nabble.com/solr-java-lang-NullPointerException-on-select-queries-tp3989974p3991400.html Sent from the Solr - User mailing list archive at Nabble.com.
