[jira] Commented: (LUCENE-555) Index Corruption

[ http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12375996 ] Erik Hatcher commented on LUCENE-555: - Could you share a test case that demonstrates this issue? > Index Corruption > > > Key: LUCENE-555 >

[jira] Commented: (LUCENE-555) Index Corruption

[ http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12376071 ] dan commented on LUCENE-555: Yes, I have a 1.6GB FSDirectory that you can try to optimize yourself. How would you like to receive the file? BTW, it doesn't matter 'how' an index

[jira] Commented: (LUCENE-555) Index Corruption

[ http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12376073 ] Yonik Seeley commented on LUCENE-555: - > Yes, I have a 1.6GB FSDirectory that you can try to optimize yourself. So are the steps to reproduce as simple as 1) optimize t

[jira] Commented: (LUCENE-555) Index Corruption

[ http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12376075 ] robert engels commented on LUCENE-555: -- I think Dan is way off base here. If complete fault tolerance is needed, he should develop it (and contribute it!). Many users a

[jira] Commented: (LUCENE-555) Index Corruption

[ http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12376078 ] Otis Gospodnetic commented on LUCENE-555: - I agree with Robert. Also, Dan, 1.6GB is quite large. I don't think anyone will be copying that and debugging it for you. W

[jira] Commented: (LUCENE-554) Possible index corruption if crashing while replacing segments file

[ http://issues.apache.org/jira/browse/LUCENE-554?page=comments#action_12376080 ] Otis Gospodnetic commented on LUCENE-554: - Looking forward to the patch. Indeed, File's renameTo may not be atomic according to its javadoc. Would a simple change th

[jira] Commented: (LUCENE-552) NPE during mergeSegments

[ http://issues.apache.org/jira/browse/LUCENE-552?page=comments#action_12376081 ] Otis Gospodnetic commented on LUCENE-552: - Can you write a self-contained unit test that demonstrates the bug? Please attach it to this issue. > NPE during mergeSegm

[jira] Commented: (LUCENE-555) Index Corruption

[ http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12376090 ] dan commented on LUCENE-555: Robert says: "complete fault tolerance" and "automatically recover". Robert, I used none of these terms. You did. Every database, open source or not,

[jira] Commented: (LUCENE-555) Index Corruption

[ http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12376094 ] Daniel Naber commented on LUCENE-555: - Lucene is not a database. If you need a database, use a database. > Index Corruption > > > Key: LUCENE-55

[jira] Commented: (LUCENE-555) Index Corruption

[ http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12376095 ] Doug Cutting commented on LUCENE-555: - Dan, Lucene has never had a recovery mechanism other than rebuilding the index. This is usually practical, since Lucene is not mea

[jira] Commented: (LUCENE-555) Index Corruption

[ http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12376097 ] robert engels commented on LUCENE-555: -- First off, your statement "Lucene must be able to repair a corrupt index" would imply to most people "complete fault tolerance". M

[jira] Commented: (LUCENE-555) Index Corruption

[ http://issues.apache.org/jira/browse/LUCENE-555?page=comments#action_12376115 ] Chuck Williams commented on LUCENE-555: --- I'm surprised that an optimize led to a corrupt index. Other than the non-atomic rename problem, there isn't anything else in L