On Fri, May 19, 2017 at 11:50 AM, Vojtech Juranek <vjura...@redhat.com> wrote:
> On středa 17. května 2017 16:56:25 CEST Tristan Tarrant wrote: > > 2) Need a way to "rollback" the process in case of failures during the > > migration: redirecting the clients back to the original cluster without > > data loss. This would use the above L4 strategy. > > it's not only about redirecting clients - IIRC newly created entries on > target > cluster are not propagated back to source cluster during rolling upgrade, After the latest changes, new entries written to the target cluster are supposed to propagated back to the source [1]. Did you find any issue with it? [1] https://issues.jboss.org/browse/ISPN-7586 Thanks, Gustavo > so > we need also somehow sync these new data back to source cluster during the > rollback to avoid data losses. Same applies to "cancel process" feature > _______________________________________________ > infinispan-dev mailing list > infinispan-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev >
_______________________________________________ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
