从Ribbon迁移Spring Cloud LoadBalancer时Feign报服务无实例的配置咨询
迁移Spring Cloud LoadBalancer后503报错的配置修正方案
问题根因
所有以currency-exchange-service.ribbon.*为前缀的配置属于Ribbon专属配置项,在已关闭Ribbon、切换为Spring Cloud LoadBalancer的场景下,这些配置不会被读取生效。由于没有手动指定currency-exchange-service的可用实例列表,LoadBalancer缓存的目标服务实例为空,最终触发无可用实例的503报错。
替换后可正常运行的application.properties配置
# 基础服务配置 spring.application.name=currency-conversion-service server.port=8100 # 彻底禁用Eureka注册中心相关能力 eureka.client.register-with-eureka=false eureka.client.fetch-registry=false eureka.client.enabled=false # 关闭LoadBalancer内置的Ribbon配置兼容逻辑 spring.cloud.loadbalancer.ribbon.enabled=false # 为currency-exchange-service指定静态可用实例(替代原Ribbon的listOfServers配置) spring.cloud.loadbalancer.clients.currency-exchange-service.static-config.instances[0].host=localhost spring.cloud.loadbalancer.clients.currency-exchange-service.static-config.instances[0].port=8000 spring.cloud.loadbalancer.clients.currency-exchange-service.static-config.instances[0].scheme=http spring.cloud.loadbalancer.clients.currency-exchange-service.static-config.instances[1].host=localhost spring.cloud.loadbalancer.clients.currency-exchange-service.static-config.instances[1].port=8001 spring.cloud.loadbalancer.clients.currency-exchange-service.static-config.instances[1].scheme=http
配置注意事项
- 所有遗留的
ribbon前缀配置(包括原注释掉的currency-exchange-service.ribbon.listOfServers、currency-exchange-service.ribbon.eureka.enabled)均可直接删除,这类配置在LoadBalancer场景下不会被加载,无任何实际作用,仅会增加配置冗余 - 需确保项目依赖中已引入
spring-cloud-starter-loadbalancer,且Feign组件的负载均衡能力已由该组件提供,不会回退加载Ribbon实现 - 上述静态实例配置为Spring Cloud LoadBalancer原生能力,无需依赖注册中心即可生效
内容的提问来源于stack exchange,提问作者Ash
相关产品推荐
相关产品推荐

