You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello maintainers,
I would appreciate clarification on the primary/replica setup. From what I gather, there should be a single primary only. Any number of replicas that would download the token store from the primary on start.
Say I enable writable token store on both primary and replicas. The primary is at primary example com, and many replicas are behind a loadbalancer at replica.example.com. The loadbalancer uses simple random routing. What happens if i try to upload a token to replica.example.com? Would the primary now contain the uploaded token? In other words, is the primary's sole purpose a source for new replicas to sync up to?
The text was updated successfully, but these errors were encountered:
Hello maintainers,
I would appreciate clarification on the primary/replica setup. From what I gather, there should be a single primary only. Any number of replicas that would download the token store from the primary on start.
Say I enable writable token store on both primary and replicas. The primary is at primary example com, and many replicas are behind a loadbalancer at replica.example.com. The loadbalancer uses simple random routing. What happens if i try to upload a token to replica.example.com? Would the primary now contain the uploaded token? In other words, is the primary's sole purpose a source for new replicas to sync up to?
The text was updated successfully, but these errors were encountered: