These are chat archives for spring-cloud/spring-cloud

7th
Jan 2016
Matt Benson
@mbenson
Jan 07 2016 17:21
I'm doing some integration testing with Eureka, for which I programmatically register and de-register services as part of the test setup and teardown. I have successfully used eureka.client.registryFetchIntervalSeconds and eureka.client.cacheRefreshExecutorExponentialBackOffBound to get the DiscoveryClient to detect the registered services and complete the test in a reasonable amount of time, but when testing the LoadBalancerClient I have to include a poll for the available server in order for the test to pass, which routinely takes about 36s, despite my having attempted to tweak eureka.client.instanceInfoReplicationIntervalSeconds, eureka.client.initialInstanceInfoReplicationIntervalSeconds, eureka.instance.leaseRenewalIntervalInSeconds, and eureka.client.heartbeatExecutorExponentialBackOffBound. What am I missing that would speed up the population of the server list?
Marcin Grzejszczak
@marcingrzejszczak
Jan 07 2016 18:57
@englishbreeze - coming back to spring-cloud/spring-cloud-sleuth#96 once I had a similar issue. In my pom.xml instead of instead of ${spring-cloud-netflix.version} I entered spring-cloud-netflix.version
maybe you have the same situation
englishbreeze
@englishbreeze
Jan 07 2016 19:13
@marcingrzejszczak Apparently doing a mvn clean resolved that error
Marcin Grzejszczak
@marcingrzejszczak
Jan 07 2016 19:20
cool
englishbreeze
@englishbreeze
Jan 07 2016 21:08
@marcingrzejszczak -Thanks for the help, the services are getting correlated now.
Marcin Grzejszczak
@marcingrzejszczak
Jan 07 2016 22:00
Awesome I'm really happy to hear that
Matt Benson
@mbenson
Jan 07 2016 22:23
interestingly, with no seemingly substantive changes, my DiscoveryClient tests now take almost as long to finish as my LoadBalancerClient tests. :/