Kine doesn't enumerate all shards when populating DB
Open
Nobody has claimed this yet.
postmortem-action-item
- Dominant language
- JavaScript
- Stars
- 18
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
This is noted in https://github.com/mapbox/cardiogram-processor/issues/277#issuecomment-547575621 in response to https://paper.dropbox.com/doc/Postmortem-Telemetry-SEV-3-cardiogram-outage-2019-10-15-2100-thru-2019-10-16-0000--AnnYD8k95Y73DFHnQA8U7vNRAg-3Hnrnq6ue6QsUxfM9S6rB.
cc @camilosanin @l-r
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
The issue names no files, tests, or entry points. Start by tracing Kine’s AWS Kinesis shard enumeration while populating the database; done means all shards are discovered and represented, with a regression test if the project has one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100