jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig <mic...@gmail.com>
Subject Re: [jr3 trade consistency for availability]
Date Tue, 28 Feb 2012 14:12:41 GMT

On 23.2.12 11:43, Michael Dürig wrote:
>>> - 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).

Again, Apache Zookeeper might be worth looking into if we decide to 
implement ACP.


> Michael

View raw message