search

xmidt-org / codex-deploy

Codex provides a historical context about devices connected to XMiDT.
Apache License 2.0
5 stars 8 forks source link

Add DB Fail Over List #62

Closed kcajmagic closed 5 years ago

kcajmagic commented 5 years ago

If the database cluster the package is talking to goes down, there should be a back up list of clusters to try.

Think of it as a primary cluster and a backup list. So if the primary cluster comes back, the active connection should go from the backup list back to the primary.

kristinapathak commented 5 years ago

Think of it as a primary cluster and a backup list. So if the primary cluster comes back, the active connection should go from the backup list back to the primary.

We need a configurable interval for when to ping the primary cluster to check if it's back. Also, I think we need an ordered list, otherwise different svalinns may fall back to different clusters, causing issues (only a problem if we are supposed to insert only to one region).

kcajmagic commented 5 years ago

Yes, I agree.

kristinapathak commented 5 years ago

Closing this as it is not needed anymore.