Prepare resources for compiling, installing, and running Nebula Graph¶

This topic describes the requirements and suggestions for compiling and installing Nebula Graph, as well as how to estimate the resource you need to reserve for running a Nebula Graph cluster.

Reading guide¶

If you are reading this topic with the questions listed below, click them to jump to their answers.

• What do I need to compile Nebula Graph?

• What do I need to run Nebula Graph in a test environment?

• What do I need to run Nebula Graph in a production environment?

• How much memory and disk space do I need to reserve for my Nebula Graph cluster?

Requirements for compiling the Nebula Graph source code¶

Hardware requirements for compiling Nebula Graph¶

Supported operating systems for compiling Nebula Graph¶

For now, we can only compile Nebula Graph in the Linux system. We recommend that you use any Linux system with kernel version 2.6.32 or above.

Software requirements for compiling Nebula Graph¶

You must have the correct version of the software listed below to compile Nebula Graph. If they are not as required or you are not sure, follow the steps in Prepare software for compiling Nebula Graph to get them ready.

Other third-party software will be automatically downloaded and installed to the build directory at the configure (cmake) stage.

Prepare software for compiling Nebula Graph¶

This section guides you through the downloading and installation of software required for compiling Nebula Graph.

1. Install dependencies.

   • For CentOS, RedHat, and Fedora users, run the following commands.

     $ yum update
     $ yum install -y make \
                      m4 \
                      git \
                      wget \
                      unzip \
                      xz \
                      readline-devel \
                      ncurses-devel \
                      zlib-devel \
                      gcc \
                      gcc-c++ \
                      cmake \
                      gettext \
                      curl \
                      redhat-lsb-core \
                      bzip2
       // For CentOS 8+, RedHat 8+, and Fedora, install libstdc++-static and libasan as well
     $ yum install -y libstdc++-static libasan
     

   • For Debian and Ubuntu users, run the following commands.

     $ apt-get update
     $ apt-get install -y make \
                          m4 \
                          git \
                          wget \
                          unzip \
                          xz-utils \
                          curl \
                          lsb-core \
                          build-essential \
                          libreadline-dev \
                          ncurses-dev \
                          cmake \
                          gettext
     

2. Check if the GCC and cmake on your host are in the right version. See Software requirements for compiling Nebula Graph for the required versions.

   $ g++ --version
   $ cmake --version
   

   If your GCC and CMake are in the right version, then you are all set. If they are not, follow the sub-steps as follows.

   1. Clone the nebula-common repository to your host.

    ```bash
    $ git clone -b 2.5.1 https://github.com/vesoft-inc/nebula-common.git
    ```
   
    Users can use the `--branch` or `-b` option to specify the branch to be cloned. For example, for 2.5.1, run the following  command.
   
    ```bash
    $ git clone --branch v2.5.1 https://github.com/vesoft-inc/nebula-common.git
    ```
   

   2. Make nebula-common the current working directory.

    ```bash
    $ cd nebula-common
    ```
   

   3. Run the following commands to install and enable CMake and GCC.

    ```bash
    // Install CMake.
    $ ./third-party/install-cmake.sh cmake-install
   
    // Enable CMake.
    $ source cmake-install/bin/enable-cmake.sh
   
    // Authorize the write privilege to the opt directory.
    $ sudo mkdir /opt/vesoft && sudo chmod -R a+w /opt/vesoft
   
    // Install GCC. Installing GCC to the opt directory requires the write privilege. And users can change it to other locations.
    $ ./third-party/install-gcc.sh --prefix=/opt
   
    // Enable GCC.
    $ source /opt/vesoft/toolset/gcc/7.5.0/enable
   ```
   

3. Execute the script install-third-party.sh.

   $ ./third-party/install-third-party.sh
   

Requirements and suggestions for installing Nebula Graph in test environments¶

Hardware requirements for test environments¶

Supported operating systems for test environments¶

For now, we can only install Nebula Graph in the Linux system. To install Nebula Graph in a test environment, we recommend that you use any Linux system with kernel version 3.9 or above.

Suggested service architecture for test environments¶

For example, for a single-machine test environment, you can deploy 1 metad, 1 storaged, and 1 graphd processes in the machine.

For a more common test environment, such as a cluster of 3 machines (named as A, B, and C), you can deploy Nebula Graph as follows:

Requirements and suggestions for installing Nebula Graph in production environments¶

Hardware requirements for production environments¶

Supported operating systems for production environments¶

For now, we can only install Nebula Graph in the Linux system. To install Nebula Graph in a production environment, we recommend that you use any Linux system with kernel version 3.9 or above.

Users can adjust some of the kernel parameters to better accommodate the need for running Nebula Graph. For more information, see kernel configuration.

Suggested service architecture for production environments¶

Each metad process automatically creates and maintains a replica of the metadata. Usually, you need to deploy three metad processes and only three.

The number of storaged processes does not affect the number of graph space replicas.

Users can deploy multiple processes on a single machine. For example, on a cluster of 5 machines (named as A, B, C, D, and E), you can deploy Nebula Graph as follows:

Capacity requirements for running a Nebula Graph cluster¶

Users can estimate the memory, disk space, and partition number needed for a Nebula Graph cluster of 3 replicas as follows.

• Question 1: Why do we multiply the disk space and memory by 120%?

  Answer: The extra 20% is for buffer.

• Question 2: How to get the number of RocksDB instances?

  Answer: Each directory in the --data_path item in the etc/nebula-storaged.conf file corresponds to a RocksDB instance. Count the number of directories to get the RocksDB instance number.

  Note

  Users can decrease the memory size occupied by the bloom filter by adding --enable_partitioned_index_filter=true in etc/nebula-storaged.conf. But it may decrease the read performance in some random-seek cases.

FAQ¶

About storage devices¶

Nebula Graph is designed and implemented for NVMe SSD. All default parameters are optimized for the SSD devices and require extremely high IOPS and low latency.

• Due to the poor IOPS capability and long random seek latency, HDD is not recommended. Users may encounter many problems when using HDD.

• Do not use remote storage devices, such as NAS or SAN. Do not connect an external virtual hard disk based on HDFS or Ceph.

• Do not use RAID.

• Use local SSD devices.

About CPU architecture¶