How to add two nodes to a single node Vertica cluster
search cancel

How to add two nodes to a single node Vertica cluster

book

Article ID: 227889

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

Currently we have only one node DR server, we need to add two new servers to make a total of 3 nodes DR servers cluster.

What is the correct process when adding two nodes to a single node Data Repository (DR) Vertica cluster?

When turning a single node DR cluster into a 3 node DR cluster do you add both nodes at the same time? Do you add both nodes one at a time?

Environment

All supported DX NetOps Performance Management releases

Resolution

The specific steps and instructions for adding a node to an existing DR cluster are found in the Add a Node to the Data Repository Cluster section.

When adding a single node to an existing DR cluster follow those steps from start to finish.

When adding two nodes to an existing DR cluster some steps can be done simultaneously. Some steps must be done individually, to each new host one at a time. The high level steps when adding two nodes at the same time are as follows. The specific steps/commands for each are found in the Add a Node to the Data Repository Cluster documentation.

  1. Complete the Prerequisites on both new nodes
    • Can be done simultaneously or one after the other
  2. Prepare the New Host on both new hosts
    • Can be done simultaneously or one after the other
  3. Add a Host to the Cluster
    • Add one new host completing it's Vertica install.
    • Add second new host completing it's Vertica install
    • Complete each individually, one after the other.
    • Don't run the installs simultaneously
  4. Add a Node to the Database
    • This step done via the Vertica adminTools UI should present both new cluster hosts to be added at the same time.
  5. Create the Buddy Projection
    • Done to DB as a whole.
    • Not node specific.
  6. Update the Data Repository Configuration
    • Ensure both nodes are specified in the configuration.
    • Ensure the DA dadaemon is restarted after the change