jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig <mdue...@apache.org>
Subject Re: [jr3 trade consistency for availability]
Date Thu, 23 Feb 2012 11:43:21 GMT

>> - Atomicity of save operations?
> how does a temporary violation of atomic saves look like?
> are you thinking of partially visible changes?

I actually had clustering on my mind where the repository is partitioned 
across various cluster nodes. If we require atomicity for save operation 
across partitions we will need to implement some form of atomic 
commitment protocol (i.e. two phase commit). This can cause blocking in 
the face of network failures (i.e. less availability).


View raw message