spring-cloud / spring-cloud/spring-cloud-gateway

Timeout for Eureka Registered Services

Open
#2,695 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

waiting for votes
Dominant language
Java
Stars
4.9k
Forks
3.5k
Avg merge
20h 57m
Merged PRs (30d)
8

Description

Right now, we can configure timeout (connect, response) for individual routes configured in our application.yml, but there is no provision to set timeouts for route configured via Eureka. When we enable the discovery client we can route to other services registered on same eureka server. In our usecase, we want to configure individual timeouts for different services.
Tried overriding route by passing same route_id : ReactiveCompositeDiscoveryClient_<APP_NAME> but doesn't seems to work.

Simple hack we are doing right now is explicitly defining route for services for which we need different timeout and setting order with higher precedence with a downside of having multiple entries for same route (obviously with different precedence)

We were able to configure timeout with ribbon easily in zuul, however in spring cloud gateway & loadbalancer this doesn't seems to be possible.

Is there any plan around this?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how Eureka discovery routes are generated and how timeout settings are applied to explicitly configured routes in application.yml. Compare the discovery-client route behavior with the existing duplicate-route workaround; done should mean different Eureka-registered services can receive individual timeouts without manually defining duplicate routes.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring, spring-boot
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.