<div dir="ltr">On Fri, May 19, 2017 at 11:50 AM, Vojtech Juranek <span dir="ltr"><<a href="mailto:vjuranek@redhat.com" target="_blank">vjuranek@redhat.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">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, </blockquote><div><br></div><div>After the latest changes, new entries written to the target cluster are supposed to propagated back to the source [1].<br><br></div><div>Did you find any issue with it?<br></div><div><br><div><br>[1] <a href="https://issues.jboss.org/browse/ISPN-7586">https://issues.jboss.org/browse/ISPN-7586</a><br></div><br></div><div>Thanks,<br></div><div>Gustavo<br></div><br><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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></div>