scylladb / scylladb/alternator-client-javascript
Ensure that decomission and dead node scenarios are handled properly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 45m
- Merged PRs (30d)
- 5
Description
Jira task: https://scylladb.atlassian.net/browse/DRIVER-686
Jira epic: https://scylladb.atlassian.net/browse/DRIVER-38
Copied from Jira epic DRIVER-38:
We need to make sure that dynamodb requests are not failing when node is being decommissioned from the cluster.
Instead failed http request has to be retried on another host.
Idea of advanced handling logic:
- Have a success and error metrics for all the nodes
- When request is failing client adds to error metric based on what error is it
- When requests are failing on certain node put them in the list of broken nodes and exclude from list of active nodes
- Once on a while allow request to be routed to the broken node to see if it is back to normal
- If such requests succeeds remove node from list of broken node
Migrated from GitHub issue: https://github.com/scylladb/alternator-load-balancing/issues/98
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 payload names no files, tests, or entry points. Start by reading the linked Jira task and epic, then the migrated issue; done means DynamoDB requests continue during node decommissioning by retrying failed HTTP requests on another host.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100