Indexing error: System.IO.IOException: read past EOF

[James Tan]

We are getting the indexing error, build 2874. Reset server still the same.

2014-07-11 00:13:34.7771,Raven.Database.Indexing.AbstractIndexingExecuter,Warn,Failed to index documents for index: {index name},"System.InvalidOperationException: Could not properly write to index ... ---> System.IO.IOException: read past EOF

   at Lucene.Net.Store.BufferedIndexInput.Refill() in c:\Work\lucene.net\src\core\Store\BufferedIndexInput.cs:line 179

   at Lucene.Net.Store.BufferedIndexInput.ReadByte() in c:\Work\lucene.net\src\core\Store\BufferedIndexInput.cs:line 42

   at Lucene.Net.Store.ChecksumIndexInput.ReadByte() in c:\Work\lucene.net\src\core\Store\CheckSumIndexInput.cs:line 42

   at Lucene.Net.Store.IndexInput.ReadInt() in c:\Work\lucene.net\src\core\Store\IndexInput.cs:line 77

   at Lucene.Net.Index.SegmentInfos.Read(Directory directory, String segmentFileName) in c:\Work\lucene.net\src\core\Index\SegmentInfos.cs:line 280

   at Lucene.Net.Index.IndexFileDeleter..ctor(Directory directory, IndexDeletionPolicy policy, SegmentInfos segmentInfos, StreamWriter infoStream, DocumentsWriter docWriter, HashSet`1 synced) in c:\Work\lucene.net\src\core\Index\IndexFileDeleter.cs:line 202

   at Lucene.Net.Index.IndexWriter.Init(Directory d, Analyzer a, Boolean create, IndexDeletionPolicy deletionPolicy, Int32 maxFieldLength, IndexingChain indexingChain, IndexCommit commit) in c:\Work\lucene.net\src\core\Index\IndexWriter.cs:line 1305

   at Lucene.Net.Index.IndexWriter.Init(Directory d, Analyzer a, IndexDeletionPolicy deletionPolicy, Int32 maxFieldLength, IndexingChain indexingChain, IndexCommit commit) in c:\Work\lucene.net\src\core\Index\IndexWriter.cs:line 1203

   at Lucene.Net.Index.IndexWriter..ctor(Directory d, Analyzer a, IndexDeletionPolicy deletionPolicy, MaxFieldLength mfl) in c:\Work\lucene.net\src\core\Index\IndexWriter.cs:line 5441

   at Raven.Database.Indexing.RavenIndexWriter.CreateIndexWriter() in c:\Builds\RavenDB-Stable\Raven.Database\Indexing\RavenIndexWriter.cs:line 122

   at Raven.Database.Indexing.Index.CreateIndexWriter() in c:\Builds\RavenDB-Stable\Raven.Database\Indexing\Index.cs:line 469

   at Raven.Database.Indexing.Index.Write(Func`4 action) in c:\Builds\RavenDB-Stable\Raven.Database\Indexing\Index.cs:line 373

   --- End of inner exception stack trace ---

   at Raven.Database.Indexing.Index.Write(Func`4 action) in c:\Builds\RavenDB-Stable\Raven.Database\Indexing\Index.cs:line 440

   at Raven.Database.Indexing.SimpleIndex.IndexDocuments(AbstractViewGenerator viewGenerator, IndexingBatch batch, IStorageActionsAccessor actions, DateTime minimumTimestamp) in c:\Builds\RavenDB-Stable\Raven.Database\Indexing\SimpleIndex.cs:line 176

   at Raven.Database.Indexing.IndexStorage.Index(String index, AbstractViewGenerator viewGenerator, IndexingBatch batch, WorkContext context, IStorageActionsAccessor actions, DateTime minimumTimestamp) in c:\Builds\RavenDB-Stable\Raven.Database\Indexing\IndexStorage.cs:line 854

   at Raven.Database.Indexing.IndexingExecuter.IndexDocuments(IStorageActionsAccessor actions, String index, IndexingBatch batch) in c:\Builds\RavenDB-Stable\Raven.Database\Indexing\IndexingExecuter.cs:line 324"

[James Tan]

The Index data folder now has CommitPoints folder that time-stamped the time this index start failing. Can this be used for recovery? If so how?

Thanks

James

[James Tan]

Based on http://help.octopusdeploy.com/discussions/problems/11285-unable-to-add-machines-indexing-errors-in-ravendb

and https://issues.apache.org/jira/browse/LUCENENET-383

It sounds this is, in fact, a lucene issue but needs better handling in RavenDB, at least, if this is not self-recoverable, it shall throw error not WARN.

Thanks

James

[Oren Eini (Ayende Rahien)]

That is a known transient error, to my recollection. It would fail in this, then recover.

Is this stopping your indexig?

Oren Eini

CEO

Mobile: + 972-52-548-6969

Office:  + 972-4-622-7811

Fax:      + 972-153-4622-7811

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[James Tan]

Yes, this index stopped, every new entry after the first failure could not be indexed  for two days and did not self recovery. Restarted db didnot help.

Thanks

James

You received this message because you are subscribed to a topic in the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ravendb/j7WYOq8NHMk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ravendb+u...@googlegroups.com.

[Oren Eini (Ayende Rahien)]

Can you send us the db?

[vi...@platinumtechnologyinc.com]

This error was causing the RavenDB  backup to not complete and deleting the index was the only option.

[Oren Eini (Ayende Rahien)]

This is a post from two years ago. I don't think that it is still relevant

Hibernating Rhinos Ltd  

Oren Eini l CEO l Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811