spring-cloud / spring-cloud/spring-cloud-zookeeper
Properties reload costs a lot
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 574
- Forks
- 408
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 4
Description
https://github.com/spring-cloud/spring-cloud-zookeeper/blob/90fac586e2c05b9f17caf5be7ab7cc79403e924e/spring-cloud-zookeeper-config/src/main/java/org/springframework/cloud/zookeeper/config/ConfigWatcher.java#L113
if we have large number of configurations and a config is updated ， all application nodes will pull the full configuration , which is too expensive.
Shall we add a cache with listener?
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 with spring-cloud-zookeeper-config/src/main/java/org/springframework/cloud/zookeeper/config/ConfigWatcher.java around line 113. Trace how a configuration update causes application nodes to pull the full configuration, then investigate the proposed cache and listener design. Done means updates avoid unnecessary full configuration pulls while preserving correct configuration propagation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- cloud, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100