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

Always use worker for server? #27

Open
ronag opened this issue Mar 7, 2021 · 2 comments
Open

Always use worker for server? #27

ronag opened this issue Mar 7, 2021 · 2 comments

Comments

@ronag
Copy link
Contributor

ronag commented Mar 7, 2021

If worker is available. Would it make sense to always run the server inside a Worker and even have the "leader" client act like a "follower" in relation to the worker?

@ronag
Copy link
Contributor Author

ronag commented Mar 7, 2021

Also another way to pick the leader could be to check isMaster (cluster + worker) and make it so that the master is always the leader. We can skip the live retry that way?

Could maybe be achieve in user space with an option.

@vweevers
Copy link
Member

vweevers commented Mar 7, 2021

If worker is available. Would it make sense to always run the server inside a Worker and even have the "leader" client act like a "follower" in relation to the worker?

We need to fix Level/leveldown#667 (and possibly other issues) before level(down) can be used in a worker.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

2 participants