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.

Sign up for GitHub

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

Jump to bottom

Update 2.meta-service.md #622

Merged
merged 1 commit into from
Aug 24, 2021
Merged

Update 2.meta-service.md #622

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs-2.0/1.introduction/3.nebula-graph-architecture/2.meta-service.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
# Meta Service

This article will introduce the architecture and functions of the Meta Service.
This topic introduces the architecture and functions of the Meta Service.

## The architecture of the Meta Service

The architecture of the Meta Service is as follows:

![The architecture of the Meta Service](https://docs-cdn.nebula-graph.com.cn/docs-2.0/1.introduction/2.nebula-graph-architecture/meta-architecture1.png)

The Meta Service is run by the nebula-metad processes. Users can deploy nebula-metad processes according to the scenario:
The Meta Service is run by nebula-metad processes. Users can deploy nebula-metad processes according to the scenario:

* In a test environment, users can deploy one or three nebula-metad processes on different machines or a single machine.
* In a production environment, we recommend that users deploy three nebula-metad processes on different machines for high availability.
Expand Down