generator-jhipster: Setting up Ribbon's Connection timeout in microservice environment

Here is my config, maybe we should consider adding to generated yml files.

zuul:
    host:
        connect-timeout-millis: 5000
        socket-timeout-millis: 10000

hystrix:
    command:
        default:
            execution:
                isolation:
                    thread:
                        timeoutInMilliseconds: 10000

Just add below snippet at application.yml where located at gateway-ms that works perfect

hystrix: 
  command: 
    default: 
      execution: 
        isolation: 
          thread: 
            timeoutInMilliseconds: 30000
ribbon: 
  ReadTimeout: 60000
  connection-timeout: 3000
  eureka: 
    enabled: true
zuul: 
  host: 
    connect-timeout-millis: 5000
    max-per-route-connections: 10000
    max-total-connections: 5000
    socket-timeout-millis: 60000
  semaphore: 
    max-semaphores: 500

We had this issue too. One of our microservices was taking ~3 seconds to complete, so 90% of the time we would get the timeout error even though the service completed successfully.

Out of the box, Ribbon’s ReadTimeout, and ConnectTimeout are both 1000. These values are found in RibbonClientConfiguration.java

The Ribbon timeout is calculated in AbstractRibbonCommand.java:

ribbonTimeout = (ribbonReadTimeout + ribbonConnectTimeout) * (maxAutoRetries + 1) * (maxAutoRetriesNextServer + 1);

maxAutoRetries and maxAutoRetriesNextServer values are found in DefaultClientConfigImpl.java

We updated our gateway’s application.yml and added:

ribbon:
    ReadTimeout: 4000

This keeps the ribbonTimeout calculation at 10000 which matches the value of hystrix.command.default.execution.isolation.thread.timeoutInMilliseconds.

(4000 + 1000) * (0 + 1) * (1 + 1)

This avoids receiving errors like this:

gateway-app_1 | 2018-11-14 15:54:36.072 WARN 1 --- [ XNIO-2 task-16] o.s.c.n.z.f.r.s.AbstractRibbonCommand : The Hystrix timeout of 10000ms for the command microservice is set lower than the combination of the Ribbon read and connect timeout, 12000ms.

Finally, the Ribbon property names are case sensitive, ie ReadTimeout, not read-timeout, or readTimeout.

@PierreBesson I can do that. Where would the best place be to put this?

Here is what I read to make it work:

https://github.com/spring-cloud/spring-cloud-netflix/issues/321