[infinispan-dev] IgnoreExtraResponsesValidityFilter

2012-01-13 Thread Manik Surtani
Looking at IgnoreExtraResponsesValidityFilter - this seems to be a scalability 
issue!  It seems to copy a set of every address in the cluster and gradually 
remove entries as responses come in.  Isn't this a scalability issue?  Since - 
assuming a large cluster - for every prepare command, we create a collection, 
copy into it the entire list of addresses (think hundreds of nodes x hundreds 
of concurrent threads) only to "count down" on the responses.  I'm almost 
certain there is a better way to do this!  :)  Maybe even maintain a shared 
list of members (updated whenever there is a view change) to test for responses 
from non-members, a counter, and assume that members don't respond to the same 
request more than once?

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

2012-01-13 Thread Galder Zamarreño
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

2012-01-13 Thread Galder Zamarreño
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

2012-01-13 Thread Manik Surtani
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


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

2012-01-13 Thread Galder Zamarreño
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

2012-01-13 Thread Manik Surtani
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


[infinispan-dev] 5.1 documentation

2012-01-13 Thread Galder Zamarreño
Hi all,

With final just around the corner, could individual owners of articles in 
https://docs.jboss.org/author/display/ISPN check that they content up to date 
information?

Please remember that we know have old versions of documentation (i.e. 
https://docs.jboss.org/author/display/ISPN50/Home), so the documentation should 
really contain latest info.

I think it's Ok though to mention that this or that change is active since 
version x.y.z, but anything else should be left to old docs.

Thanks in advance!
--
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