<div dir="ltr"><div><div><div><div><div><div><div><div><div>+1 for Vojtech<br><br></div>yes the client's need to moved to the new cluster in one shot current, that was discussed before.<br></div>And it makes the migration because most of the customers are not able to make that happen.<br></div>So there is a small possibility of inconsistence if clients connect to the old server update entries until the new server already migrated it.<br><br></div>I see two options<br>1)<br></div>source server need to propagate active to target on update<br>2)<br></div>with the new L4 strategy all clients are moved automatically to the target. So the source is not updated.<br></div>I only see a small possibility for this to happen during switch<br></div>- a client might still have a request to the source until other clients are moved to target and already accessed the key<br></div>- a new client connects with old properties, here we need to ensure that the first request is redirected to the target and not update the source<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 19, 2017 at 12:50 PM, Vojtech Juranek <span dir="ltr"><<a href="mailto:vjuranek@redhat.com" target="_blank">vjuranek@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On středa 17. května 2017 16:56:25 CEST Tristan Tarrant wrote:<br>
> 2) Need a way to "rollback" the process in case of failures during the<br>
> migration: redirecting the clients back to the original cluster without<br>
> data loss. This would use the above L4 strategy.<br>
<br>
</span>it's not only about redirecting clients - IIRC newly created entries on target<br>
cluster are not propagated back to source cluster during rolling upgrade, so<br>
we need also somehow sync these new data back to source cluster during the<br>
rollback to avoid data losses. Same applies to "cancel process" feature<br>______________________________<wbr>_________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/infinispan-<wbr>dev</a><br></blockquote></div><br></div>