diff --git a/3.6.0/index.html b/3.6.0/index.html index 51cb8302e89..e9ed283059e 100644 --- a/3.6.0/index.html +++ b/3.6.0/index.html @@ -5737,7 +5737,7 @@

Welcome to NebulaGraph 3.6.0 Documentation

Note

-

This manual is revised on 2023-10-30, with GitHub commit 095118b400.

+

This manual is revised on 2023-10-30, with GitHub commit f488eba609.

NebulaGraph is a distributed, scalable, and lightning-fast graph database. It is the optimal solution in the world capable of hosting graphs with dozens of billions of vertices (nodes) and trillions of edges (relationships) with millisecond latency.

Getting started

diff --git a/3.6.0/nebula-operator/1.introduction-to-nebula-operator/index.html b/3.6.0/nebula-operator/1.introduction-to-nebula-operator/index.html index 70a5cfc33bd..b10949765b9 100644 --- a/3.6.0/nebula-operator/1.introduction-to-nebula-operator/index.html +++ b/3.6.0/nebula-operator/1.introduction-to-nebula-operator/index.html @@ -5072,13 +5072,6 @@ Version limitations - - -
  • - - Feature limitations - -
  • @@ -5735,13 +5728,6 @@ Version limitations - - -
  • - - Feature limitations - -
  • @@ -5837,8 +5823,6 @@

    Version limitationsFeature limitations

    -

    The NebulaGraph Operator scaling feature is only available for the Enterprise Edition of NebulaGraph clusters and does not support scaling the Community Edition version of NebulaGraph clusters.

    Release note

    Release

    diff --git a/3.6.0/nebula-operator/2.deploy-nebula-operator/index.html b/3.6.0/nebula-operator/2.deploy-nebula-operator/index.html index 85a82b03d5a..1f61c0a08cd 100644 --- a/3.6.0/nebula-operator/2.deploy-nebula-operator/index.html +++ b/3.6.0/nebula-operator/2.deploy-nebula-operator/index.html @@ -5835,7 +5835,7 @@

    Prerequisites

    Note

    +

    See community cluster configurations.

    +

    The following table describes the parameters in the sample configuration file.

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    ParameterDefault valueDescription
    metadata.name-The name of the created NebulaGraph cluster.
    spec.console-Configuration of the Console service. For details, see nebula-console.
    spec.graphd.replicas1The numeric value of replicas of the Graphd service.
    spec.graphd.imagevesoft/nebula-graphdThe container image of the Graphd service.
    spec.graphd.versionv3.6.0The version of the Graphd service.
    spec.graphd.service-The Service configurations for the Graphd service.
    spec.graphd.logVolumeClaim.storageClassName-The log disk storage configurations for the Graphd service.
    spec.metad.replicas1The numeric value of replicas of the Metad service.
    spec.metad.imagevesoft/nebula-metadThe container image of the Metad service.
    spec.metad.versionv3.6.0The version of the Metad service.
    spec.metad.dataVolumeClaim.storageClassName-The data disk storage configurations for the Metad service.
    spec.metad.logVolumeClaim.storageClassName-The log disk storage configurations for the Metad service.
    spec.storaged.replicas3The numeric value of replicas of the Storaged service.
    spec.storaged.imagevesoft/nebula-storagedThe container image of the Storaged service.
    spec.storaged.versionv3.6.0The version of the Storaged service.
    spec.storaged.dataVolumeClaims.resources.requests.storage-Data disk storage size for the Storaged service. You can specify multiple data disks to store data. When multiple disks are specified, the storage path is /usr/local/nebula/data1, /usr/local/nebula/data2, etc.
    spec.storaged.dataVolumeClaims.resources.storageClassName-The data disk storage configurations for Storaged. If not specified, the global storage parameter is applied.
    spec.storaged.logVolumeClaim.storageClassName-The log disk storage configurations for the Storaged service.
    spec.storaged.enableAutoBalancetrueWhether to balance data automatically.
    spec.<metad|storaged|graphd>.securityContext{}Defines privilege and access control settings for NebulaGraph service containers. For details, see SecurityContext.
    spec.agent{}Configuration of the Agent service. This is used for backup and recovery as well as log cleanup functions. If you do not customize this configuration, the default configuration will be used.
    spec.reference.name-The name of the dependent controller.
    spec.schedulerName-The scheduler name.
    spec.imagePullPolicyThe image policy to pull the NebulaGraph image. For details, see Image pull policy.The image pull policy in Kubernetes.
    spec.logRotate-Log rotation configuration. For more information, see Manage cluster logs.
    spec.enablePVReclaimfalseDefine whether to automatically delete PVCs and release data after deleting the cluster. For more information, see Reclaim PVs.
  • Create a NebulaGraph cluster.

    @@ -5817,9 +5928,7 @@

    Create clustersScaling clusters

    - +

    The cluster scaling feature is for NebulaGraph Enterprise Edition only.

    Delete clusters

    Run the following command to delete a NebulaGraph cluster with Kubectl:

    -

    Output:

    -
    NAME                READY   STATUS    RESTARTS   AGE
    -nebula-graphd-0     1/1     Running   0          5m34s
    -nebula-graphd-1     1/1     Running   0          5m34s
    -nebula-metad-0      1/1     Running   0          5m34s
    -nebula-metad-1      1/1     Running   0          5m34s
    -nebula-metad-2      1/1     Running   0          5m34s
    -nebula-storaged-0   1/1     Running   0          5m34s
    -nebula-storaged-1   1/1     Running   0          5m34s
    -nebula-storaged-2   1/1     Running   0          5m34s
    -
  • Scaling clusters

    - +

    The cluster scaling feature is for NebulaGraph Enterprise Edition only.

    Delete clusters

    Run the following command to delete a NebulaGraph cluster with Helm: