On Dec 4, 2012, at 10:22 AM, Sanne Grinovero <[email protected]> wrote:
> On 4 December 2012 09:14, Galder Zamarreño <[email protected]> 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. Precisely, which is why I raised the flag instead of going down the easy path. > > 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. The problem is considering when a cluster is formed. How many nodes should you wait for? There's already plans for something similar: https://issues.jboss.org/browse/ISPN-928 > I'd prefer the getCache() to block for long enough. > > Sanne > > _______________________________________________ > infinispan-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/infinispan-dev -- Galder Zamarreño [email protected] twitter.com/galderz Project Lead, Escalante http://escalante.io Engineer, Infinispan http://infinispan.org _______________________________________________ infinispan-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/infinispan-dev
