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

add-dynamic-changes-to-configs #1994

Merged
merged 1 commit into from
Mar 13, 2023
Merged

add-dynamic-changes-to-configs #1994

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
14 changes: 12 additions & 2 deletions ....0/nebula-operator/8.custom-cluster-configurations/8.1.custom-conf-parameter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Meta, Storage, and Graph services in a NebulaGraph Cluster have their configurat

The structure of `config` is as follows.

```
```go
Config map[string]string `json:"config,omitempty"`
```
## Prerequisites
Expand Down Expand Up @@ -56,12 +56,22 @@ The following example uses a cluster named `nebula` and the cluster's configurat
"auth_type": "password"
...
```

To add the `config` for the Meta and Storage services, add `spec.metad.config` and `spec.storaged.config` respectively.

3. Run `kubectl apply -f nebula_cluster.yaml` to push your configuration changes to the cluster.

After customizing the parameters `enable_authorize` and `auth_type`, the configurations in the corresponding ConfigMap (`nebula-graphd`) of the Graph service will be overwritten.

## Modify cluster configurations online

Cluster configurations are modified online by calling the HTTP interface, without the need to restart the cluster Pod.

It should be noted that only when all configuration items in `config` are the parameters that can be dynamically modified at runtime, can the operation of online modifications be triggered. If the configuration items in `config` contain parameters that cannot be dynamically modified, then the cluster configuration will be updated by restarting the Pod.

For information about the parameters that can be dynamically modified for each service, see the parameter table column of **Whether supports runtime dynamic modifications** in [Meta service configuration parameters](../../5.configurations-and-logs/1.configurations/2.meta-config.md), [Storage service configuration parameters](../../5.configurations-and-logs/1.configurations/4.storage-config.md), and [Graph service configuration parameters](../../5.configurations-and-logs/1.configurations/3.graph-config.md), respectively.

## Learn more

For more information on the configuration parameters of Meta, Storage, and Graph services, see [Configurations](../../5.configurations-and-logs/1.configurations/1.configurations.md).
For more information about the configuration parameters of Meta, Storage, and Graph services, see [Meta service configuration parameters](../../5.configurations-and-logs/1.configurations/2.meta-config.md), [Storage service configuration parameters](../../5.configurations-and-logs/1.configurations/4.storage-config.md), and [Graph service configuration parameters](../../5.configurations-and-logs/1.configurations/3.graph-config.md).