ZF-5531: CLONE -Concurrent adding and committing throws 'Zend_Search_Lucene_Exception' File XXX.del is not readable.
Description
I am still getting this error using the current trunk, rev 13605.
my system information: Kernel 2.6.18-6-686 32bit PHP 5.2.6 Apache 2.2.9 Ext3 Local mounted FS
Comments
Posted by Jurrien Stutterheim (norm2782) on 2009-01-13T07:36:26.000+0000
Upped priority to critical
Posted by Jurrien Stutterheim (norm2782) on 2009-01-13T07:38:08.000+0000
Added link to older issues
Posted by Mark Henderson (markh) on 2009-01-18T23:52:22.000+0000
We're experiencing this issue too and are hoping that 1.7.3 fixes it, as 1.7.2 is definitely still broken.
Posted by Mark Henderson (markh) on 2009-01-21T08:11:17.000+0000
We're still getting this error in 1.7.3, but slightly less frequently. Here's the trace:
Error occurred in Search while trying to findHits. Reason: File '/var/www/htdocs/mobilize/tenants/0002/tmp/search/index-group-669/_4qc_1.del' is not readable Type of Exception thrown: Zend_Search_Lucene_Exception Code: 0 File: /usr/share/php/ZendFramework-1.7.3-minimal/library/Zend/Search/Lucene/Storage/File/Filesystem.php Line: 59 Trace: #0 /usr/share/php/ZendFramework-1.7.3-minimal/library/Zend/Search/Lucene/Storage/Directory/Filesystem.php(358): Zend_Search_Lucene_Storage_File_Filesy
1 /usr/share/php/ZendFramework-1.7.3-minimal/library/Zend/Search/Lucene/Index/SegmentInfo.php(370): Zend_Search_Lucene_Storage_Directory_Filesystem->getFile
2 /usr/share/php/ZendFramework-1.7.3-minimal/library/Zend/Search/Lucene.php(467): Zend_Search_Lucene_Index_SegmentInfo->__construct(Object(Zend_Search_Lucen
3 /usr/share/php/ZendFramework-1.7.3-minimal/library/Zend/Search/Lucene.php(537): Zend_Search_Lucene->_readSegmentsFile()
4 /usr/share/php/ZendFramework-1.7.3-minimal/library/Zend/Search/Lucene.php(208): Zend_Search_Lucene->__construct('/var/www/htdocs...', false)
Posted by Alexander Veremyev (alexander) on 2009-01-30T08:23:44.000+0000
Fixed.
Posted by Jürgen Mangler (juergen.mangler@univie.ac.at) on 2009-01-30T09:40:42.000+0000
I'm skeptical, this bug has been marked fixed every single last 500 releases :-) Let's see if this time its finally really fixed.
Posted by Mark Henderson (markh) on 2009-02-03T16:30:32.000+0000
We're still testing under load, but it seems to be fixed for us too. Thank you!
Posted by old of Satoru Yoshida (yoshida@zend.co.jp) on 2009-04-01T05:49:11.000+0000
correct fix version