Re: [infinispan-dev] 5.0 to 5.1 upgrade gotchas
There's no doc as such yet. I was thinking of compiling them all in this dev thread and then put them in a doc while doing the final release... On Jan 13, 2012, at 3:22 PM, Manik Surtani wrote: 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@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Manik Surtani ma...@jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
Re: [infinispan-dev] 5.0 to 5.1 upgrade gotchas
Yeah, i'll open it asap. More stuff, hierarchical changes for RemoteCache and RemoteCacheManager: http://infinispan.blogspot.com/2011/11/more-locking-improvements-in-infinispan.html On Jan 13, 2012, at 3:32 PM, Manik Surtani wrote: Ok. Well, we may as well start the doc and all of us add to it … On 13 Jan 2012, at 14:28, Galder Zamarreño wrote: There's no doc as such yet. I was thinking of compiling them all in this dev thread and then put them in a doc while doing the final release... On Jan 13, 2012, at 3:22 PM, Manik Surtani wrote: 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@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Manik Surtani ma...@jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Manik Surtani ma...@jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
Re: [infinispan-dev] 5.0 to 5.1 upgrade gotchas
Here it is: https://docs.jboss.org/author/display/ISPN/Upgrading+from+5.0+to+5.1 On Jan 13, 2012, at 4:44 PM, Galder Zamarreño wrote: Yeah, i'll open it asap. More stuff, hierarchical changes for RemoteCache and RemoteCacheManager: http://infinispan.blogspot.com/2011/11/more-locking-improvements-in-infinispan.html On Jan 13, 2012, at 3:32 PM, Manik Surtani wrote: Ok. Well, we may as well start the doc and all of us add to it … On 13 Jan 2012, at 14:28, Galder Zamarreño wrote: There's no doc as such yet. I was thinking of compiling them all in this dev thread and then put them in a doc while doing the final release... On Jan 13, 2012, at 3:22 PM, Manik Surtani wrote: 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@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Manik Surtani ma...@jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Manik Surtani ma...@jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
Re: [infinispan-dev] 5.0 to 5.1 upgrade gotchas
On Jan 11, 2012, at 3:25 PM, Sérgio Miguel Fernandes wrote: On 10 Jan 2012, at 12:29, Galder Zamarreño wrote: On Jan 10, 2012, at 12:59 PM, Sérgio Miguel Fernandes wrote: I guess this is also a 5.0 to 5.1 issue: https://issues.jboss.org/browse/ISPN-1696 In what way is that an upgrade issue? That's just a newly added XML element, nothing that in principiple should affect upgrades. I had a config file for 5.0 using optimistic transactions with repeatable read and write skew check enabled. When upgrading that project to 5.1, I had to turn on versioning to be able to use write skew detection. I could not do it, because of the mentioned bug in the parser, hence the upgrade issue. Ah, I see what you mean now :) - Yup, that constitutes a gotcha. -- Sérgio Miguel Fernandes ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
Re: [infinispan-dev] 5.0 to 5.1 upgrade gotchas
Hi, On 9 Jan 2012, at 10:26, Galder Zamarreño wrote: 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. I guess this is also a 5.0 to 5.1 issue: https://issues.jboss.org/browse/ISPN-1696 Cheers, -- Sérgio Miguel Fernandes ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
Re: [infinispan-dev] 5.0 to 5.1 upgrade gotchas
That's a bug. It's fixed in CR3 :-) On 10 Jan 2012, at 11:59, Sérgio Miguel Fernandes wrote: Hi, On 9 Jan 2012, at 10:26, Galder Zamarreño wrote: 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. I guess this is also a 5.0 to 5.1 issue: https://issues.jboss.org/browse/ISPN-1696 Cheers, -- Sérgio Miguel Fernandes ___ 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
Re: [infinispan-dev] 5.0 to 5.1 upgrade gotchas
Just did it: https://issues.jboss.org/browse/ISPN-1695 On Jan 9, 2012, at 12:37 PM, Manik Surtani wrote: On 9 Jan 2012, at 10:27, Galder Zamarreño wrote: ^, btw, this gotcha could be removed by making the parser deal with wakeUpInterval in eviction and passing it onto the expiration element. Should be simple to do and removes a headache. +1. Create a JIRA for this? It should be a dead-easy patch. -- Manik Surtani ma...@jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño Sr. Software Engineer Infinispan, JBoss Cache ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
Re: [infinispan-dev] 5.0 to 5.1 upgrade gotchas
On 9 Jan 2012, at 10:56, Mircea Markus wrote: Default transaction enlistment is now Synchronisation (vs XAResource). No it's not - I haven't submitted that pull request yet. The work is in my topic branch https://github.com/maniksurtani/infinispan/tree/t_1284 but I have concerns around this, hence the email thread on synchronisations and rollbacks. Cheers Manik -- Manik Surtani ma...@jboss.org twitter.com/maniksurtani Lead, Infinispan http://www.infinispan.org ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
Re: [infinispan-dev] 5.0 to 5.1 upgrade gotchas
On 9 Jan 2012, at 13:38, Manik Surtani wrote: On 9 Jan 2012, at 10:56, Mircea Markus wrote: Default transaction enlistment is now Synchronisation (vs XAResource). No it's not - I haven't submitted that pull request yet. The work is in my topic branch https://github.com/maniksurtani/infinispan/tree/t_1284 but I have concerns around this, hence the email thread on synchronisations and rollbacks. ok. ___ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
