How to get 'rid' of indexing error, and how it came there

113 views
Skip to first unread message

Lars Corneliussen

unread,
Nov 25, 2015, 5:59:57 AM11/25/15
to RavenDB - 2nd generation document database

How to get rid of such an error without having to reset the whole index?

I did already resave the doc... If it is still an issue, shouldn't also the error come up again?


Or is the doc not watched anymore?


Michael Yarichuk

unread,
Nov 25, 2015, 6:06:30 AM11/25/15
to RavenDB - 2nd generation document database
Looks a bit weird. Can you show the index definition?
Does this reproduces?

Also, can you check for full stack trace of this exception?

--
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.



--
Best regards,

 

Michael Yarichuk

RavenDB Core Team

Tel: 972-4-6227811

Fax:972-153-4-6227811

Email : michael....@hibernatingrhinos.com

 

RavenDB paving the way to "Data Made Simple" http://ravendb.net/  

Grisha Kotler

unread,
Nov 25, 2015, 7:03:03 AM11/25/15
to rav...@googlegroups.com
Reproduced. The error wasn't removed.


Hibernating Rhinos Ltd  cid:image001.png@01CF95E2.8ED1B7D0

Grisha Kotler l RavenDB Core Team Developer Mobile: +972-54-586-8647

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

RavenDB paving the way to "Data Made Simplehttp://ravendb.net/

Oren Eini (Ayende Rahien)

unread,
Nov 25, 2015, 9:06:55 AM11/25/15
to ravendb
That is by design, actually. The error is in the _index_, which allows it.
The error will be removed if the index definition is updated

Hibernating Rhinos Ltd  

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

On Wed, Nov 25, 2015 at 12:59 PM, Lars Corneliussen <m...@lcorneliussen.de> wrote:

Lars Corneliussen

unread,
Nov 25, 2015, 9:11:38 AM11/25/15
to RavenDB - 2nd generation document database
The given key was not present in the dictionary.

How can this error happen without a single square-bracket / dictionary-access in the index definition?
Stacktrace would be helpful - but I know, not too easy with Linq.

Oren Eini (Ayende Rahien)

unread,
Nov 25, 2015, 9:14:36 AM11/25/15
to ravendb
Look at the logs, the full error is there

Oren Eini (Ayende Rahien)

unread,
Nov 25, 2015, 9:15:02 AM11/25/15
to ravendb
Note that this error was raised by an index batcher, not the index itself

Lars Corneliussen

unread,
Nov 25, 2015, 9:26:52 AM11/25/15
to RavenDB - 2nd generation document database
In the error logs I only found these errors and warnings (which I neither understand)...

But the times of occurance do not correlate.

System.AggregateException: One or more errors occurred. ---> Raven.Abstractions.Exceptions.IndexDoesNotExistsException: There is no index with id: 64
at Raven.Database.Storage.Esent.StorageActions.DocumentStorageActions.UpdateLastIndexed(Int32 id, Etag etag, DateTime timestamp) in c:\Builds\RavenDB-Stable-3.0\Raven.Database\Storage\Esent\StorageActions\Indexing.cs:line 229


and

Message
Failed to execute indexing
Exception
System.AggregateException: One or more errors occurred. ---> Raven.Abstractions.Exceptions.IndexDoesNotExistsException: There is no index with id: 64
   at Raven.Database.Storage.Esent.StorageActions.DocumentStorageActions.UpdateLastIndexed(Int32 id, 


and three times  (with different index id)

Message
Failure running post filter index action for index with no docs to execute
Exception
Raven.Abstractions.Exceptions.IndexDoesNotExistsException: There is no index with id: 37
   at Raven.Database.Storage.Esent.StorageActions.DocumentStorageActions.UpdateLastIndexed(Int32 id, 

Oren Eini (Ayende Rahien)

unread,
Nov 25, 2015, 10:24:28 AM11/25/15
to ravendb
This all looks like stuff that happens if you deleted an index while it was indexing.

Lars Corneliussen

unread,
Nov 26, 2015, 9:34:26 AM11/26/15
to RavenDB - 2nd generation document database
The "index can't be found"-errors happened at 03:06 AM - hopefully I wasn't sleepwalking.

Oren Eini (Ayende Rahien)

unread,
Nov 29, 2015, 4:12:39 AM11/29/15
to ravendb
Can you check the logs for what index that was?
It is possible that an idle index was deleted by the db.

Lars Corneliussen

unread,
Oct 17, 2016, 6:29:02 AM10/17/16
to RavenDB - 2nd generation document database
hm. i still have these errors. now with an index that doesn'f have a scripted index result script attached at all!

this is in the logs....


2016-10-17 12:14:48.4277,Raven.Database.Prefetching.PrefetchingBehavior,Warn,,"After early exit: Got 68 documents (96 kb) in a future batch, starting from etag 01000000-0000-0E46-0000-000000012935 to etag 01000000-0000-0E46-0000-000000012978, took 27ms",
2016-10-17 12:16:16.5213,Raven.Database.Indexing.Index.Indexing,Warn,,"Error when executed OnIndexEntryCreated trigger for index 'ReplacementOf/***', key: '******'","System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Raven.Database.Bundles.ScriptedIndexResults.ScriptedIndexResultsIndexTrigger.Batcher.OnIndexEntryCreated(String entryKey, Document document) in c:\Builds\RavenDB-Stable-3.0\Raven.Database\Bundles\ScriptedIndexResults\ScriptedIndexResultsIndexTrigger.cs:line 80
   at Raven.Database.Extensions.EnumerableExtensions.ApplyAndIgnoreAllErrors[T](IEnumerable`1 self, Action`1 errorAction, Action`1 action) in c:\Builds\RavenDB-Stable-3.0\Raven.Database\Extensions\EnumerableExtensions.cs:line 35"
2016-10-17 12:16:38.6582,Raven.Database.Config.MemoryStatistics,Warn,,"Low memory detected, will try to reduce memory usage...",
2016-10-17 12:16:38.6582,Raven.Database.Config.MemoryStatistics,Error,,Failure to process low memory notification (low memory handler - Raven.Database.Indexing.SimpleIndex),
2016-10-17 12:16:38.6582,Raven.Database.Config.MemoryStatistics,Error,,Failure to process low memory notification (low memory handler - Raven.Database.Indexing.MapReduceIndex),
2016-10-17 12:16:38.6582,Raven.Database.Config.MemoryStatistics,Error,,Failure to process low memory notification (low memory handler - Raven.Database.Indexing.SimpleIndex),


We're running on build 30115

Oren Eini (Ayende Rahien)

unread,
Oct 18, 2016, 3:10:47 AM10/18/16
to ravendb
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages