Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of mreutegg@adobe.com designates
 64.18.1.187 as permitted sender)
From: Marcel Reutegger <mreutegg@adobe.com>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Date: Thu, 7 Mar 2013 11:57:03 +0000
Subject: RE: SegmentNodeStore merge operations
Thread-Topic: SegmentNodeStore merge operations
Thread-Index: Ac4bJrLEAGOgf+CmS0ypySnmDYqLDgAAxsAQ
Message-ID: 
 <9C0FC4C8E9C29945B01766FC7F9D3898178B1A624F@eurmbx01.eur.adobe.com>
References: 
 <CAOFYJNY4fOy2bq_Sysj11RawdwU9UBQsULq=Uas6ftGf1TogpA@mail.gmail.com>
 <CD5E1298.3D6E4%mueller@adobe.com>
 <CAOFYJNbJG5vz1YeL=mEzNBZhNbV8O_Zukj=+XCZqUgdMvF0L=w@mail.gmail.com>
 <9C0FC4C8E9C29945B01766FC7F9D3898178B1A6247@eurmbx01.eur.adobe.com>
 <CAOFYJNZXRTNBhvMJG_5gnFxViLaC00ot=m2xBuwPQr08uCKHfQ@mail.gmail.com>
In-Reply-To: 
 <CAOFYJNZXRTNBhvMJG_5gnFxViLaC00ot=m2xBuwPQr08uCKHfQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> On Thu, Mar 7, 2013 at 1:08 PM, Marcel Reutegger <mreutegg@adobe.com>
> wrote:
> > as mentioned before, I think snapshot isolation is just fined because
> > in most cases it is sufficient and allows for increased concurrency. fo=
r
> > the cases where more consistency guarantees are needed, like
> > unique UUIDs and hard references we should implement the
> > validators accordingly and e.g. use a technique like materializing the
> conflict.
>=20
> That technique essentially serializes all commits that could possibly
> violate a global invariant.

not necessarily. e.g. if we take the unique UUID as an example,
two sessions can proceed concurrently when they create nodes
with different UUIDs, which is usually the case. the conflict only
materializes when you create two nodes with the same UUID.

> The SegmentMK can avoid such
> synchronization points entirely at the cost of potentially "undoing"
> some commits that become invalid later on.

doesn't this require knowledge about the internals of the global
invariant. how does the SegmentMK know what exactly it can undo?

regards
 marcel