Archive
Archive
To start an empty VoltDB database on a cluster, you will need the following information for the voltdb create command:
Deployment file location: The deployment file defines the cluster configuration including the number of nodes. The deployment file must be identical on all nodes for the cluster to start, so be sure you copy the deployment file to all nodes of the cluster. We’ll describe details about the deployment file in Section 3.6, “Defining the Cluster Configuration”.
Host name: Provide the hostname or IP address of the cluster’s host node, which coordinates the startup of all the nodes in the cluster.
License file location: If you are using the VoltDB Enterprise Edition, provide a license file on the host node. Only the host node requires the license file when starting a cluster.
For each node of the cluster, log in and start the server process using the same command. For example, the following voltdb create command starts the database cluster specifying the location and name of the deployment file and naming voltsvr1 as the host node. Be sure the number of nodes on which you run the command match the number of nodes defined in the deployment file.
$ voltdb create --deployment=deployment.xml -–host=voltsvr1
Or you can also use shortened forms for the argument flags:
$ voltdb create -d deployment.xml -H voltsvr1
VoltDB looks for the license file on the host as a file named license.xml in three locations, in
the following order:
The current working directory
The directory where the VoltDB image files are installed (usually in the /voltdb subfolder of
the installation directory)
The current user's home directory
If the license file is not in any of these locations, you must explicitly identify it when you run the
voltdb command on the host node using the --license or -l flag. For
example, the command on the host node might be:
V5.x Documentation$ voltdb create -d deployment.xml -H voltsvr1 \
-l /usr/share/voltdb-license.xmlWhen starting a VoltDB database on a cluster, the VoltDB server process performs the following actions:
If you are starting the database on the node identified as the host node, it waits for initialization messages from the remaining nodes. The host can be any node in the cluster and plays a special role during startup by managing the cluster initiation process. It is important that all nodes in the cluster can resolve the hostname or IP address of the host node you specify.
If you are starting the database on a non-host node, it sends an initialization message to the host indicating that it is ready. The database is not operational until the correct number of nodes (as specified in the deployment file) have connected.
Once all the nodes have sent initialization messages, the host sends out a message to the other nodes that the cluster is complete. Once the startup procedure is complete, the host's role is over and it becomes a peer like every other node in the cluster. It performs no further special functions.
Manually logging on to each node of the cluster every time you want to start the database can be tedious. Instead, you can use secure shell (ssh) to execute shell commands remotely. By creating an ssh script (with the appropriate permissions) you can copy files and/or start the datab ase on each node in the cluster from a single script.