spring-cloud / spring-cloud/spring-cloud-zookeeper
Wait until ApplicationReadyEvent to register
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 574
- Forks
- 408
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 4
Description
Use Zuul with ZookeeperDiscovery, and Zuul return 404 when deploying services. The reason seems that ZookeeperDiscovery register service in start of LifeCycle. In that time, the container has no beed fully started so that any request returns 404.
Is there any work around to delay registration of ZookeeperDiscovery?
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing ZookeeperDiscovery registration through its lifecycle and comparing that timing with Spring Boot's ApplicationReadyEvent while reproducing the Zuul 404 during deployment. No files or tests are named; done means service registration waits until the application is ready and requests no longer receive 404 responses during startup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100