Multi-portal failover with Compose.io
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 17.6k
- Forks
- 2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 40
Description
- Version: 2.8.0
- Platform: Node.js 10.15.3 on Ubuntu 18.04
- Description:
Is it possible to configure NodeRedis to handle failover with multiple portals? Compose.io gives you two connection strings:
redis://[username]:[password]@aws-us-east-1-portal.35.dblayer.com:31156
redis://[username]:[password]@aws-us-east-1-portal.36.dblayer.com:31156
It is expected that you can fail over to one or the other if one of your portals stop working. It isn't clear from the documentation if this sort of behavior is supported out of the box. If it is, how do I configure the connection string to do this?
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 reading the NodeRedis connection documentation and searching the repository for existing failover, portal, or multiple-endpoint support. Determine whether Compose.io's two connection strings are supported and identify the expected configuration or missing behavior. Done means the support status and configuration are documented, or a scoped implementation plan is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, redis, typescript
- Domain
- backend, databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100