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

Discover storage service automatically on meta server-side. #283

Closed
dangleptr opened this issue Apr 18, 2019 · 2 comments
Closed

Discover storage service automatically on meta server-side. #283

dangleptr opened this issue Apr 18, 2019 · 2 comments
Assignees
Milestone

Comments

@dangleptr
Copy link
Contributor

dangleptr commented Apr 18, 2019

Currently, we use "addHost" to register all storage daemons after init the whole cluster.
We should support discover storage service automatically in meta-server side.

Subtask of #182

@dangleptr dangleptr changed the title Discover storage service automatically in meta server-side. Discover storage service automatically on meta server-side. Apr 18, 2019
@sherman-the-tank
Copy link
Member

Totally agree that only "addHost" mechanism is definitely not enough. Just thinking about the case that we restart the meta service

One possible solution is to rely on the storage service's periodical schema/parts allocation pulling request.

@sherman-the-tank
Copy link
Member

Is this still valid?

The current solution is to use "ADD HOST" manually maintain the cluster and use the heartbeat to automatically detect the live storage service

@sherman-the-tank sherman-the-tank added this to the v1_beta_release milestone May 30, 2019
yixinglu added a commit to yixinglu/nebula that referenced this issue Mar 21, 2022
* Cancel memory check when the ratio greater than 1.0

* Comment

Co-authored-by: Yichen Wang <[email protected]>

Co-authored-by: Yee <[email protected]>
Co-authored-by: Yichen Wang <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants