Aggregator continues to collect data if `record` process crashes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
I'm just discovering a state at UCSD where the aggregator record process has crashed due to some type error, but new data coming in continues to get added to the data queue. Since the aggregator version is fairly old, it's possible that the type error may be fixed, but I think the behavior of data being added to the queue when record is not running probably still exists.
I think we probably want this behavior so we don't lose data on crash, but we should probably be setting a max queue size to limit memory usage.
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 aggregator's record process and the data queue implementation. Confirm whether data continues to accumulate after record crashes, then determine an appropriate maximum queue size and verify that the queue remains bounded without losing data during normal operation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100