Hi Pedro,
May I steal this implementation for improving xsite replication? =)
Erik
-Original Message-
From: infinispan-dev-boun...@lists.jboss.org
[mailto:infinispan-dev-boun...@lists.jboss.org] On Behalf Of Pedro Ruivo
Sent: Monday, March 18, 2013 12:10 PM
To: ispn-dev
Subject: [infinis
That's certainly doable, but we have the opposite problem too:
Some docu of the 5.2 is not there yet AFAIK:
- Non-blocking state transfer, segments…
- Is x-site replication docu there? I don't mean design docu, but user docu.
So, happy to fork, once all the 5.2 docu has been completed…
Cheers,
I've done some research after you pointed it out. Didn't know that
pseudo-javadoc existed, and thinking the code that generated it was
related to the JAXB stuff, I removed it.
Tristan
On 03/18/2013 05:35 PM, Sanne Grinovero wrote:
> On 18 March 2013 16:30, Tristan Tarrant wrote:
>> Unfortunate
On 18 March 2013 16:30, Tristan Tarrant wrote:
> Unfortunately in my over-eager axing of the doclets in infinispan-tools,
> the Schema doclet got chewed.
> I will reinstate it asap.
>
> Tristan
>
> On 03/18/2013 05:28 PM, Galder Zamarreño wrote:
>> Why outdated? What would be the new way to lookup
Unfortunately in my over-eager axing of the doclets in infinispan-tools,
the Schema doclet got chewed.
I will reinstate it asap.
Tristan
On 03/18/2013 05:28 PM, Galder Zamarreño wrote:
> Why outdated? What would be the new way to lookup that info?
>
> On Mar 14, 2013, at 10:37 PM, Sanne Grinover
Why outdated? What would be the new way to lookup that info?
On Mar 14, 2013, at 10:37 PM, Sanne Grinovero wrote:
> Apparently I have been using an "outdated" way to lookup information
> for the configuration;
> i.e.
> http://docs.jboss.org/infinispan/5.1/configdocs/
> and
> http://docs.jboss.or
Hi all,
To solve ISPN-2808 (avoid blocking JGroups threads in order to allow to
deliver the request responses), I've created another thread pool to move
the possible blocking commands (i.e. the commands that may block until
some state is achieved).
Problem description:
With this solution, the
http://transcripts.jboss.org/meeting/irc.freenode.org/infinispan/2013/infinispan.2013-03-18-14.57.html
Cheers,
--
Galder Zamarreño
gal...@redhat.com
twitter.com/galderz
Project Lead, Escalante
http://escalante.io
Engineer, Infinispan
http://infinispan.org
__
> there should
> be no need to use a ClusterCacheLoader,
I agree. This looked consistent w/ what I saw a couple weeks ago in a
different thread. Use of ClusterCacheLoader didn't make sense to me
either...
On Mar 18, 2013, at 5:55, Sanne Grinovero wrote:
> I'm glad you're finding a workaround f
On 03/18/2013 01:21 PM, Galder Zamarreño wrote:
> Hi all,
>
> A heads up on what is going on with https://issues.jboss.org/browse/ISPN-2281
>
> While discussing this, Tristan and I came to the conclusion that we could
> avoid the need to create some wrappers required to fulfill requirements in
>
Anyone please?
On 8 March 2013 15:53, Sanne Grinovero wrote:
> Could someone make sure the documentation at
> - https://docs.jboss.org/author/display/ISPNDOC/Infinispan+Documentation
> gets forked between 5.2 and master?
>
> I need to write some updates, but these apply to master only..
>
> Chee
I'm fine with them being removed. They can be an Infinispan extension if need
be.
On 14 Mar 2013, at 09:30, Galder Zamarreño wrote:
> @Manik, thoughts?
>
> I haven't seen Infinispan cache visit listeners being used that extensively…
>
> Cheers,
>
> Begin forwarded message:
>
>> From: Greg
I'm glad you're finding a workaround for the disk IO but there should
be no need to use a ClusterCacheLoader,
the intention of that would be to be able to chain multiple grids;
this is a critical problem IMHO.
Seems there are multiple other issues at hand, let me comment per bullet:
On 18 March 2
Hi all,
A heads up on what is going on with https://issues.jboss.org/browse/ISPN-2281
While discussing this, Tristan and I came to the conclusion that we could avoid
the need to create some wrappers required to fulfill requirements in this JIRA,
and as a side effect, reduce the memory consumpti
Update:
I tried again - I think I misconfigured that ClusterCacheLoader on my
last attempt. With this configuration [1] it actually appears to be
loading keys over the network from the peer node. I'm seeing a lot of
network IO between the nodes when requesting from either one of them
(30-50 MBp/s)
15 matches
Mail list logo