cloudfoundry / cloudfoundry/loggregator-agent-release
loggregator-agent should evenly distribute traffic across Dopplers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 14
- Forks
- 34
- Avg merge
- 7h 6m
- Merged PRs (30d)
- 2
Description
Expected behavior
loggregator-agents should distribute downstream traffic among 5 downstream Dopplers, rotating those Dopplers on a reasonable cadence.
Actual behavior
The loggregator-agents will only rotate Dopplers every 100,000 batches (up to 10 million envelopes, depending on batching). Also, during upgrades or other circumstances, they can end up sending traffic to only one downstream Doppler.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named in the issue. Start by tracing how loggregator-agent batches traffic and rotates its five downstream Dopplers; done means traffic is distributed across them on a reasonable cadence, including during upgrades or other circumstances.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100