Incomplete index building

[Layle Baker]

(for Raven 2.5)

Is anyone aware of instances where an index is built, once Raven indicates the index is NOT stale anymore, the result seem incomplete:

Quick example

- Simple map (no LoadDocument - no multiple froms)

- about 300,000 documents, the index includes all of them

- once done, and get a NOT stale index status, says about 240,000 index entries

- doesn't look right, tell Raven to reset the index

- No documents are changed, but get the proper 300,000 the second time around.

Any reason why this would happen?

Thanks

Layle

[Chris Marisic]

What build/release version?

Replication?

[Layle Baker]

RavenDB 2.5 - Build #2874 - No replication