[infinispan-dev] DIST-SYNC, put(), a problem and a solution
Radim Vansa
rvansa at redhat.com
Thu Aug 7 06:50:11 EDT 2014
Hi,
the current split-brain handling design wants to sacrifice availability
(of writes) - don't worry, we don't want to break CAP and everyone here
also obeys the laws of gravity :)
Radim
On 08/07/2014 10:11 AM, ? ?????? wrote:
> Guys,
> Am I right that you trying to break CAP theorem? Seems like that
> because you want to have consistent backups (end of cache.put() means
> that primary node and all backups have the same value) and
> non-blocking behaviour (from user's POV).
> Sorry if I'm wrong.
>
> Cheers
> Alexey
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Radim Vansa <rvansa at redhat.com>
JBoss DataGrid QA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20140807/29d397be/attachment-0001.html
More information about the infinispan-dev
mailing list