Re: Indexing I/O errors and CorruptIndex messages

2017-05-04 Thread Rick Leir
Simon After hearing about the weird time issue in EC2, I am going to ask if you have a real server handy for testing. No, I have no hard facts, this is just a suggestion. And I have no beef with AWS, they have served me really well for other servers. Cheers -- Rick On May 4, 2017 10:49:25 AM

Re: Indexing I/O errors and CorruptIndex messages

2017-05-04 Thread simon
I've pretty much ruled out system/hardware issues - the AWS instance has been rebooted, and indexing to a core on a new and empty disk/file system fails in the same way with a CorruptIndexException. I can generally get indexing to complete by significantly dialing down the number of indexer scri

Re: Indexing I/O errors and CorruptIndex messages

2017-04-27 Thread simon
Nope ... huge file system (600gb) only 50% full, and a complete index would be 80gb max. On Wed, Apr 26, 2017 at 4:04 PM, Erick Erickson wrote: > Disk space issue? Lucene requires at least as much free disk space as > your index size. Note that the disk full issue will be transient, IOW > if you

Re: Indexing I/O errors and CorruptIndex messages

2017-04-26 Thread Erick Erickson
Disk space issue? Lucene requires at least as much free disk space as your index size. Note that the disk full issue will be transient, IOW if you look now and have free space it still may have been all used up but had some space reclaimed. Best, Erick On Wed, Apr 26, 2017 at 12:02 PM, simon wro