Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use etcd instead of gossip for service discovery? #50

Open
danthegoodman1 opened this issue Jul 1, 2022 · 0 comments
Open

Use etcd instead of gossip for service discovery? #50

danthegoodman1 opened this issue Jul 1, 2022 · 0 comments
Labels
question Further information is requested

Comments

@danthegoodman1
Copy link
Owner

Related to #35

If we use etcd instead for service discovery (and for locking!) then we can achive more nodes without complex gossip work.

Nodes could more aggresively update and query remote partition lengths at scale.

However the etcd cluster would have to be multi-region.

Now we need to involve etcd, and at small scale the benefits are probably not there.

@danthegoodman1 danthegoodman1 added the question Further information is requested label Jul 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant