spring-cloud / spring-cloud/spring-cloud-consul
dependency cycle when Use my own ConsulServiceRegistry with spring-boot-starter-actuator
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 822
- Forks
- 539
- Avg merge
- 9h 31m
- Merged PRs (30d)
- 7
Description
When consul set with discovery.heartbeat.enabled=true and spring-boot-starter-actuator's health endpoint enabled.
At same time, spring-boot-starter-data-mongodb also added. Use my own ConsulServiceRegistry.
Startup and comes with dependency cycle for consul's TtlScheduler!
Here is my example with logs, spring_consul_err.
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 running the linked spring_consul_err example with discovery.heartbeat.enabled=true, the Actuator health endpoint, spring-boot-starter-data-mongodb, and the custom ConsulServiceRegistry. Inspect the startup logs around Consul's TtlScheduler and dependency-cycle detection. Done means the same configuration starts without a dependency cycle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mongodb, spring-boot
- Domain
- backend, databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100