Spring-cloud-netflix: Hystrix command properties not working

[sargurgn]

hystrix.command.* properties are not taking effect. Due to default time out always the fallback method is getting called. STS also does not recognise these properties. Does the service need to be registered to eureka for hystrix command properties to work? Cant i override the fallback timeout configuration with just hystrix-starter jar?

[indrabasak]

I think your syntax is slightly incorrect. Here is what I am using:

hystrix:
    serviceA:
      execution:
        isolation:
          thread:
            timeoutInMilliseconds: 10000
    serviceB:
      execution:
        isolation:
          thread:
            timeoutInMilliseconds: 10000

[sargurgn]

@indrabasak Hi I am not using eureka.. I am just using spring-cloud-hystrix-starter. I just have one service and i don't want to use service discovery.

[indrabasak]

serviceA and serviceB are just _HystrixCommandKey_. Replace them with the names of your HystrixCommandKey. Please post your configuration (YAML file) before I make any further comment.

[christianf2029]

I have the same error with Spring Cloud Dalston.SR3 version.
I have the following hystrix dependency corresponding to this version:

<dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-starter-hystrix</artifactId>
</dependency>

The only hystrix properties available are:

hystrix:
   metrics:
     enabled: foo
     polling-interval-ms: foo

I wanted to set the isolation metrics beyond the default of 1000ms, for example:
hystrix.command.default.execution.isolation.thread.timeoutInMilliseconds: 15000
But it does not work, it does not recognize these commands .. What to do?

[ryanjbaxter]

@christianf2029 please open a separate issue

[christianf2029]

Ready @ryanjbaxter.