Book Image

HP Vertica Essentials

By : Rishabh Agrawal
Book Image

HP Vertica Essentials

By: Rishabh Agrawal

Overview of this book

<p>With the rise of Massively Parallel Processing (MPP) and NewSQL databases, many users are confused about which MPP technology to opt for. Today, HP Vertica is gaining a lot of traction as a major MPP technology. Vertica's distributed architecture allows fast query processing, and it is a highly fault-tolerant architecture, thus making it one of the most sought-after MPP databases today.</p> <p>HP Vertica Essentials will help you to learn day-to-day administration activities in a step-by-step format. You will start by learning how to install Vertica, followed by its management and monitoring. You will learn about the different backup and restore techniques, including the concept of projections in Vertica. Finally, you will explore the various techniques to improve performance and bulk loading in Vertica. By the end of this book, you will be able to install, manage, and monitor Vertica efficiently.</p>
Table of Contents (13 chapters)

Replacing nodes


If we have a K-Safe database, we can replace nodes, as a copy of the data will be maintained under the nodes. We do not need to shut down the database to replace the nodes.

Replacing a node using the same name and IP address

Sometimes, you will be required to upgrade one or more nodes in the cluster. If the new node has the same IP as the original node, then use the following method for replacement:

  1. From a working node in the cluster, run the following install_vertica script with the -s (used for providing the hostname or IP(s)) and –r (the path of the rpm/deb package) parameters:

    # /opt/vertica/sbin/install_vertica -s host -r rpm_package 
    
  2. The installation script will verify the system configuration and the installation of various important components of Vertica, such as Vertica, Spread, and the administration tool's metadata.

  3. Now, create catalog and data directories on the new node. Make sure that the path of these directories is the same as that of the original node.

  4. Once ready...