Re: [infinispan-dev] 5.0 to 5.1 upgrade gotchas

Where is this doc? On Confluence? Should add that in 5.0, commit and rollback phases were async by default. In 5.1, these are sync by default, and a short paragraph explaining why and the performance difference one may experience as a result. On 9 Jan 2012, at 10:26, Galder Zamarreño wrote: > Hi all, > > We need to document a list of gotcha's related to 5.0 to 5.1 upgrades as we prepare for final. So far I have noted these myself: > > - wakeUpInterval now defined only via expiration (XSD allowds wakeUpInterval in eviction but new parser does not) and not via eviction. > - maxEntries is the strict max but this is likely to not be reached since eviction happens per segment > - transactional vs non-transactional caches, mixed cases not allowed > > If you can think of more, reply back and we can compile them in time. > > Cheers, > -- > Galder Zamarreño > Sr. Software Engineer > Infinispan, JBoss Cache > > > _______________________________________________ > infinispan-dev mailing list > infinispan-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Manik Surtani manik(a)jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev