[infinispan-dev] public API/what should be preserve between minor releases?

[Mircea Markus]

Hi Tomas,
On 22 Nov 2012, at 08:46, Tomas Sykora wrote:

> Hi guys,
> 
> is this topic related?
> https://community.jboss.org/wiki/RollingUpgradesInInfinispan
Indirectly: in the case of rolling upgrades existing clients still need to be able to operate with new versions, which require an API compatibility. 

> 
> I'd assume that *whole* cluster will be upgraded to some higher version. Running cluster with different versions seems risky to me too. This ^^ process should be smooth but I don't know how about changes in API.
> 
> I'm very interested in this topic - that's the reason why I jumped in to your discussion.
Very interesting topic indeed. 5.2 brings support for rolling upgrades, but the way we do it is not by allowing 5.1 and 5.2 nodes to coexist in the same cluster, but by  creating a new 5.2 cluster and migrating both state and clients from the 5.1 clients to it.

> Thank you!
> 
> ----- Original Message -----
> From: "Thomas Fromm" <tf at tfromm.com>
> To: "infinispan -Dev List" <infinispan-dev at lists.jboss.org>
> Sent: Thursday, November 22, 2012 8:23:22 AM
> Subject: Re: [infinispan-dev] public API/what should be preserve between minor releases?
> 
> On 22.11.2012 04:11, Navin Surtani wrote:
>>> As you see, IMHO such API changes do not have much effect in normal
>>> situations. I can imagine only problems, when the changed methods are
>>> used within dist exec calls and there are (during update or whatever)
>>> different versions of infinispan inside the cluster.
>> Does this really happen? I'm asking purely out of ignorance but on instinct I think that running different versions on the cluster is probably a bit risky?
> 
> Thats the plan for our own software. Customer can update the nodes one 
> by one, of course only for patch releases.
> I'd expect (or at least hope) that this will be also possible with 
> infinispan in case of critical bug was fixed or smth.
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

Cheers,
-- 
Mircea Markus
Infinispan lead (www.infinispan.org)




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20121122/5371a771/attachment.html