Resolve service mirroring delay caused by RepairEndpoints
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
RepairEndpoints runs periodically to reconcile services in a multicluster environment. When the number of exported services approaches 500, RepairEndpoints runs nearly continuously which causes mirroring of services to be delayed. We need to investigate if we still need to run RepairEndpoints periodically and if there are other synchronization methods we could use.
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 locating the RepairEndpoints entry point and tracing its periodic reconciliation in the multicluster service mirroring path. Investigate whether periodic execution is necessary and compare possible synchronization methods; done means resolving the approach for avoiding mirroring delays at around 500 exported services.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100