Hi,
Re: https://issues.jboss.org/browse/ISPN-1842
Re: https://issues.jboss.org/browse/ISPN-1844
Both of these problems are rooted in the fact that both the path and the schema
name changed in 5.1.
IMO, both the path and schema should revert back to the old values. I don't see
why these should
I think a FAQ entry with a link to the bug number should be enough.
- Original Message -
> From: "Vladimir Blagojevic"
> To: "infinispan -Dev List"
> Sent: Monday, February 6, 2012 1:25:58 PM
> Subject: Re: [infinispan-dev] Eviction maxEntries analysis
>
> On 12-02-06 6:57 AM, Galder Za
- Original Message -
> From: "Dan Berindei"
> >> numOwners==2 is and will very likely remain the most common case,
> >> particularly for small clusters.
> >>
> >> But if we have two sites, it makes sense to configure 2 owners per
> >> site. If only one node goes down, the surviving owner
On 6 Feb 2012, at 13:59, Vladimir Blagojevic wrote:
> On 12-02-04 11:57 AM, Manik Surtani wrote:
>> This is very similar to storeAsBinary. If this is set to true, then keys
>> and values are serialized and stored as a MarshalledValue which contains the
>> resulting byte[]. So rather than rest
- Original Message -
> From: "Sanne Grinovero"
> To: "infinispan -Dev List"
> Sent: Monday, February 6, 2012 2:56:58 PM
> Subject: Re: [infinispan-dev] JBoss Libra
>
> On 6 February 2012 14:44, Mircea Markus wrote:
> >
> >
> > - Original Message -
> >> From: "Sanne Grinovero"
What's the actual issue at hand? Wanting to use Infinispan with Hibernate 3.6
in AS 7?
On 6 Feb 2012, at 09:53, Galder Zamarreño wrote:
> Btw, this discussion should be extended to Infinispan dev list in case we can
> improve on the custom commands SPI.
>
> In the case of Hibernate 2LC, the c
On 6 February 2012 14:44, Mircea Markus wrote:
>
>
> - Original Message -
>> From: "Sanne Grinovero"
>> To: "infinispan -Dev List"
>> Sent: Saturday, February 4, 2012 10:08:16 PM
>> Subject: Re: [infinispan-dev] JBoss Libra
>>
>> On 4 February 2012 14:57, Manik Surtani wrote:
>> > This
On Mon, Feb 6, 2012 at 3:49 PM, Mircea Markus wrote:
>> numOwners==2 is and will very likely remain the most common case,
>> particularly for small clusters.
>>
>> But if we have two sites, it makes sense to configure 2 owners per
>> site. If only one node goes down, the surviving owner will suppl
- Original Message -
> From: "Sanne Grinovero"
> To: "infinispan -Dev List"
> Sent: Saturday, February 4, 2012 10:08:16 PM
> Subject: Re: [infinispan-dev] JBoss Libra
>
> On 4 February 2012 14:57, Manik Surtani wrote:
> > This is very similar to storeAsBinary. If this is set to true,
> This is very similar to storeAsBinary. If this is set to true, then
> keys and values are serialized and stored as a MarshalledValue which
> contains the resulting byte[]. So rather than restrict to just
> byte[] types, we could restrict to:
>
> * byte[] or any other primitive, primitive arr
On 12-02-04 11:57 AM, Manik Surtani wrote:
> This is very similar to storeAsBinary. If this is set to true, then keys and
> values are serialized and stored as a MarshalledValue which contains the
> resulting byte[]. So rather than restrict to just byte[] types, we could
> restrict to:
>
>
> numOwners==2 is and will very likely remain the most common case,
> particularly for small clusters.
>
> But if we have two sites, it makes sense to configure 2 owners per
> site. If only one node goes down, the surviving owner will supply
> state to the new owner. If both nodes go down, the new
On 12-02-06 6:57 AM, Galder Zamarreño wrote:
> Vladimir, I had understood that with the new eviction logic, the only
> possible case is that the cache was evicted *before* maxEntries was reached
> cos eviction happened at the segment level.
>
> However, I'd have never expected for the cache to gr
On Mon, Feb 6, 2012 at 2:01 PM, Mircea Markus wrote:
>> We could extend the policy for craches as well, by adding a
>> minNumOwners setting and only triggering an automatic rehash when
>> there is a segment on the hash wheel with <= minNumOwners owners.
>
> minNumOwners should be at least 1, which
> We could extend the policy for craches as well, by adding a
> minNumOwners setting and only triggering an automatic rehash when
> there is a segment on the hash wheel with <= minNumOwners owners.
minNumOwners should be at least 1, which in the default use case (numOwners==2)
would mean that we
That was my understanding as well.
- Original Message -
From: "Galder Zamarreño"
To: "infinispan -Dev List"
Sent: Monday, February 6, 2012 9:57:20 AM
Subject: Re: [infinispan-dev] Eviction maxEntries analysis
Vladimir, I had understood that with the new eviction logic, the only possible
Vladimir, I had understood that with the new eviction logic, the only possible
case is that the cache was evicted *before* maxEntries was reached cos eviction
happened at the segment level.
However, I'd have never expected for the cache to grow beyon its size. If
that's the case, I think that'd
Btw, this discussion should be extended to Infinispan dev list in case we can
improve on the custom commands SPI.
In the case of Hibernate 2LC, the custom command is really a cache specific
one, so we could potentially tie up cache specific custom commands to the cache
lifecycle, but still don'
18 matches
Mail list logo
