Does your business need more storage? Consider adding nodes to your database if you need more storage. Vertica recommends that you add all new nodes at the same time.
You can use this checklist to add nodes. These are basic steps. There are additional options discussed in the Vertica documentation.
|1||Perform a full local backup of your existing database.
To include additional progress information, use the –debug option, with a value between 1–3.
|Specify a config file when you run the backup utility.
If no file exists, the backup fails with an error. Resolve the error and proceed to Step 2.
|2||Drop older or unused table partitions.
||If the table partition is dropped, proceed to Step 3.
If the table partition is not dropped, check the table name and partition value and try again.
|3||Verify that local segmentation is disabled. If it is not disabled, disable it.
||After you have confirmed that local segmentation is disabled, proceed to Step 4.|
|4||Check the network bandwidth and CPU performance of your cluster.
||Measure the latency and throughput of your network between nodes and measure the speed of consistency of your hard drives.
If the latency and throughput is lower than your initial benchmarks, contact the system administrator to fix the problems causing lower benchmarks.
|5||Check if you have enough storage (at least 40% of the size of your database) to perform the rebalance.
To get a snapshot of each node, review the following fields in the HOST_RESOURCES system table:
Confirm that the amount of disk, column, and projection storage for each node is sufficient to perform a rebalance. If so, proceed to Step 6.
If you do not have enough storage, try to reduce your catalog size. For more information, see Rebalance Taking a Long Time checklist.
|6||Minimize the DML operations on tables that are part of a rebalance. When a rebalance takes a lock on a table, a load fails.
If your rebalance might contend with ETL jobs, increase the value of the configuration parameter, LockTimeout.
||After you have addressed ongoing DML operations, proceed to Step 7.
The default value is 300 seconds (5 minutes).
|7||If your database has more than one node already, you can add a node without stopping the server. However, if you are adding a node to a single-node installation, then you must shut down both the database and spread.
||After you stop the database, proceed to Step 8.|
|8||Configure hosts and add hosts to the cluster using the update_vertica script.
||After adding nodes to the database, Vertica automatically distributes updated configuration files to the rest of the nodes in the cluster and starts the process of rebalancing data in the cluster.
After the hosts and nodes are added, proceed to Step 9.
|9||You can monitor the rebalance progress of individual tables.
||After monitoring, proceed to Step 10.|
|10||Check if rebalancing completed successfully.
||If all nodes in the cluster have rebalanced without error, you have completed this checklist.
If your rebalance did not complete successfully, contact Vertica Technical Support.
- Understanding Rebalancing, Part 1: What Happens During Rebalancing
- Understanding Rebalancing, Part 2: Optimizing for Rebalancing
- Adding Nodes