[Bug 6844] New: stable-range cache: skipping write, database drifted under my feet

[mercurial-bugs at mercurial-scm.org]

https://bz.mercurial-scm.org/show_bug.cgi?id=6844

            Bug ID: 6844
           Summary: stable-range cache: skipping write, database drifted
                    under my feet
           Product: Mercurial
           Version: 6.3.1
          Hardware: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: bug
          Priority: wish
         Component: evolution
          Assignee: bugzilla at mercurial-scm.org
          Reporter: zeger.van_de_vannet at nokia.com
                CC: mercurial-devel at mercurial-scm.org,
                    pierre-yves.david at ens-lyon.org
    Python Version: ---

When pulling from a repo (mirror server) which was pulling at that time I got
the following error:

---
remote: stable-range cache: skipping write, database drifted under my feet
remote: (disk: ac8d1535db673f2462a59b31d9931fd2e0b6b9ad-22370 vs mem:
167b64c54fecd6d5fffa0f305850429a9684b815-22367)
remote: abort: 00changelog at ac8d1535db673f2462a59b31d9931fd2e0b6b9ad: filtered
node
abort: stream ended unexpectedly (got 0 bytes, expected 4)
---


I had just pushed from my workspace (WS1) to our central server (Central).
This push triggers a pull on our local read-only mirror (Mirror), from which I
immediately tried to pull in my other workspace (WS2).

So: 

WS1 --push--> Central --pull--> Mirror --pull--> WS2

I was pushing a rather large set of commits (~500) and the Central server was
experiencing some heavy load which caused it to respond sluggishly.

I understood that these updates should be atomically and this error should not
occur.

-- 
You are receiving this mail because:
You are on the CC list for the bug.