Hilo update issue

[Media Lab]

Suddenly, and I have no idea how this happened, many Hilos for document types are lower than the highest doc Id for particular documents. For example, the Medias document had a hilo of 1744 but the highest was already 2807. I manually set the hilo to 3000 and everything started working right up until a post to AuthTokens was made & it had the same error.

This particular box is a dev box & doesn't have any sort of replication, although we've probably replicated some of its data at some point in its history.

Not sure how the hilo's got out of sync, but regardless, is there a way to have Raven automatically correct all hilos? Have it find the greatest doc id for each type and reset its particular hilo number?

[Oren Eini (Ayende Rahien)]

There isn't a way to correct all hilo automatically.

And this usually indicates that something is writing to those documents directly.

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

 

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Media Lab]

I wonder how I can figure out what that was. None of my devs are in there as far as I know and I don't have any code that writes to it. Can smuggling overwrite the hilo?

[Oren Eini (Ayende Rahien)]

Smuggler can do that, yes

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

 

On Mon, Feb 20, 2017 at 2:55 PM, Media Lab <ml.se...@medialabinc.com> wrote:

I wonder how I can figure out what that was. None of my devs are in there as far as I know and I don't have any code that writes to it. Can smuggling overwrite the hilo?

--

[Wallace Turner]

I'm also running into a similar problem now.

I restored a database into my local environment (using smuggler) and now when i attempt to save a document I am getting 

>PUT attempted on document 'foo/4213282' using a non current etag

To fix, I have manually incremented the hilo by 100k but shouldnt the restore process automatically set the HILO correctly? I have the database backup and it is 100% recreatable on build #35277

On Monday, 20 February 2017 22:05:19 UTC+8, Oren Eini wrote:

Smuggler can do that, yes

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

 

On Mon, Feb 20, 2017 at 2:55 PM, Media Lab <ml.se...@medialabinc.com> wrote:

I wonder how I can figure out what that was. None of my devs are in there as far as I know and I don't have any code that writes to it. Can smuggling overwrite the hilo?

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

[Wallace Turner]

Also, it may be the case that the database i'm restoring already has an invalid hilo.... so to provide a few more details, the following is in chronological order

1) database A created & populated

2) database A replicated to database B  (database B does not create documents)

3) database A deleted

5) database B backed up

6) database A recreated from backup B   

7) hilo error here when database A starts populating new documents