From caae78c11c0aec78ce02c426825ccd314093f355 Mon Sep 17 00:00:00 2001 From: Charles Moulliard Date: Thu, 18 May 2017 10:22:18 +0200 Subject: [PATCH] Change ServerListRefreshInterval and Hystrix timeoutInMilliseconds. Fix typo error within the README file --- .../greeting-service/src/main/resources/application.yml | 8 +++----- .../kubernetes-circuitbreaker-ribbon-example/readme.md | 2 +- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/spring-cloud-kubernetes-examples/kubernetes-circuitbreaker-ribbon-example/greeting-service/src/main/resources/application.yml b/spring-cloud-kubernetes-examples/kubernetes-circuitbreaker-ribbon-example/greeting-service/src/main/resources/application.yml index 57570c47..5017c766 100644 --- a/spring-cloud-kubernetes-examples/kubernetes-circuitbreaker-ribbon-example/greeting-service/src/main/resources/application.yml +++ b/spring-cloud-kubernetes-examples/kubernetes-circuitbreaker-ribbon-example/greeting-service/src/main/resources/application.yml @@ -11,9 +11,7 @@ backend: enabled: false client: enabled: true - # We will use Spring Cloud Kubernetes Ribbon to retrieve the list of the servers - # listOfServers: backend:8080 - ServerListRefreshInterval: 15000 + ServerListRefreshInterval: 5000 -hystrix.command.BackendCall.execution.isolation.thread.timeoutInMilliseconds: 30000 -hystrix.threadpool.BackendCallThread.coreSize: 5 \ No newline at end of file +hystrix.command.BackendCall.execution.isolation.thread.timeoutInMilliseconds: 5000 +hystrix.threadpool.BackendCallThread.coreSize: 5 diff --git a/spring-cloud-kubernetes-examples/kubernetes-circuitbreaker-ribbon-example/readme.md b/spring-cloud-kubernetes-examples/kubernetes-circuitbreaker-ribbon-example/readme.md index 4e7cd345..a06c7501 100644 --- a/spring-cloud-kubernetes-examples/kubernetes-circuitbreaker-ribbon-example/readme.md +++ b/spring-cloud-kubernetes-examples/kubernetes-circuitbreaker-ribbon-example/readme.md @@ -73,7 +73,7 @@ Hello from name-service-1-0ss0r! ``` As Ribbon will question the Kubernetes API to get, base on the `name-service` name, the list of IP Addresses assigned to the service as endpoints, -you should see that you will get a reponse from one of the 2 pods running +you should see that you will get a response from one of the 2 pods running ``` kc get endpoints/name-service