On Wed, Jul 30, 2014 at 12:35 AM, Sanne Grinovero sa...@infinispan.org
wrote:
On 29 July 2014 22:14, Dan Berindei dan.berin...@gmail.com wrote:
On Tue, Jul 29, 2014 at 9:06 PM, Sanne Grinovero sa...@infinispan.org
wrote:
This is a nasty problem and I also feel passionately we need to
On 07/30/2014 09:02 AM, Dan Berindei wrote:
if your proposal is only meant to apply to non-tx caches, you are right
you don't have to worry about multiple primary owners... most of the
time. But when the primary owner changes, then you do have 2 primary
owners (if the new primary owner
On Wed, Jul 30, 2014 at 12:00 PM, Pedro Ruivo pe...@infinispan.org wrote:
On 07/30/2014 09:02 AM, Dan Berindei wrote:
if your proposal is only meant to apply to non-tx caches, you are right
you don't have to worry about multiple primary owners... most of the
time. But when the
Investigation:
When I looked at UNICAST3, I saw a lot of missing messages on the
receive side and unacked messages on the send side. This caused me to
look into the (mainly OOB) thread pools and - voila - maxed out !
I learned from Pedro that the Infinispan
On 29/07/14 16:39, Dan Berindei wrote:
Investigation:
This mitigated the problem somewhat, but when I increased the requester
threads to 100, I had the same problem again. Apparently, the Infinispan
internal thread pool uses a rejection policy of run and
On 29/07/14 20:06, Sanne Grinovero wrote:
This is a nasty problem and I also feel passionately we need to get
rid of it ASAP.
+1
I did have the same problems many times, and we discussed this also in
Farnborough; AFAIR Dan and Pedro had some excellent ideas to fix this.
You don't need
On 29/07/14 23:14, Dan Berindei wrote:
On Tue, Jul 29, 2014 at 9:06 PM, Sanne Grinovero sa...@infinispan.org
mailto:sa...@infinispan.org wrote:
This is a nasty problem and I also feel passionately we need to get
rid of it ASAP.
I did have the same problems many times, and we
On 29/07/14 23:35, Sanne Grinovero wrote:
The strategy I've proposed is only to be applied for the communication
from the primary owner to its backups:
the value to be written is well known as it's the primary owner which
defines it unilaterally (for example if there is an atomic
On 07/30/2014 01:59 PM, Dan Berindei wrote:
On Wed, Jul 30, 2014 at 12:22 PM, Radim Vansa rva...@redhat.com
mailto:rva...@redhat.com wrote:
Investigation:
When I looked at UNICAST3, I saw a lot of missing messages on the
receive side and
Ion, Martin - what are your thoughts?
On Jul 29, 2014, at 16:34, Sanne Grinovero sa...@infinispan.org wrote:
All,
in Search we wrap the Parser in a decorator which workarounds the
classloader limitation.
I still think you should fix this, it doesn't matter how/why it was changed.
Sanne
10 matches
Mail list logo
