[infinispan-dev] Put issues with newly joining node

Sanne Grinovero sanne at infinispan.org
Tue Dec 4 04:22:54 EST 2012


On 4 December 2012 09:14, Galder Zamarreño <galder at redhat.com> wrote:
> Hey Dan/Adrian,
>
> Re: https://issues.jboss.org/browse/ISPN-2541
>
> I'm looking at this intermittent failure, and it seems to be caused by the fact that the test does not wait for the cluster to be formed when the new node is started, which can lead a replication timeout failure from the new joining node.
>
> The test can easily be fixed by waiting for cluster to form, and then do the call.
>
[...]

I don't think the cache should ever be in an illegal state to be used
after being started. So Infinispan should not require tests to wait
for a "cluster to be formed", I'd rather guarantee that after a cache
is started it's usable.

If this is not possible, then any application would also need to wait
for that "cluster formed" event, and we should expose an API for that.
I'd prefer the getCache() to block for long enough.

Sanne



More information about the infinispan-dev mailing list