[infinispan-dev] Hot Rod topology cache update retry timeout

[Mircea Markus]

Looks  good.
What is causing this unsuccessful add? If it is caused by timeouts due to multiple caches operating on the same key an alternative would be to only perform the operation on the coordinator and rest of the members to have node added listeners ... 
On 18 May 2010, at 19:03, Manik Surtani wrote:

> Fine by me.
> 
> On 18 May 2010, at 16:48, galder at redhat.com wrote:
> 
>> Hi all,
>> 
>> For https://jira.jboss.org/browse/ISPN-426 I've created a small retry logic for when there's an issue updating the topology information on startup. By default, I set the max wait time to 30 seconds and I was wondering whether this should be made user configurable. This would a parameter into startServer.sh but it'd only be relevant to the Hot Rod server.
>> 
>> The primary reason I'm considering not to make it user configurable is cos it's related to Hot Rod metadata which user should not really be aware of. If after 30 seconds, lightweight metadata hasn't been updated, something pretty wrong is going on and I doubt increasing it is going to make much difference.
>> 
>> WDYT?
>> 
>> Cheers,
>> --
>> Galder Zamarreño
>> Sr. Software Engineer
>> Infinispan, JBoss Cache
>> 
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> 
> --
> Manik Surtani
> manik at jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
> http://www.infinispan.org
> http://www.jbosscache.org
> 
> 
> 
> 
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev