Make it so bucket destroy flushes all bucket operations before destroying the bucket
Open
- Dominant language
- C++
- Stars
- 34
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Currently, bucket destroy can occur before all operations on the bucket complete. We should make a task to flush selectively only Hermes operations for a particular bucket.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the bucket-destroy path and the code that tracks or flushes Hermes operations for a bucket. Determine how destruction can race with pending operations and define completion as flushing only that bucket's Hermes operations before destruction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100