What's the biggest number of machines do we support in one group?
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 368
- Avg merge
- 19h 32m
- Merged PRs (30d)
- 3
Description
We're now using CPU + tcp + redis store in our cluster with 250 machines.
It works well when the gloo instances number is under 1k in one group, but it fails with connect refused, connect timeout when connectFullMesh() when the gloo instances number > 1k(we're using 1.5k).
So I'd like to know the biggest number of gloo instances we support in one group.
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 at connectFullMesh(), the entry point named in the report, and trace how connections behave above 1,000 instances. Reproduce the connect-refused and timeout behavior with the reported CPU, TCP, and Redis setup; done means the supported group limit and failure cause are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, redis
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100