Congratulations on needing to expand your cluster on ClustrixDB!
Your ClustrixDB is licensed for a maximum number of cores per node as well as a maximum number of nodes for the cluster. Contact Clustrix Sales to if you need an expanded license.
Provision nodes and Install ClustrixDB on each node, using the same version and installation configuration.
If zones are in use, ensure that the target configuration has an equal number of nodes in each zone.
If you are using encrypted connections, ensure that certificates in keys are present in the same location with the correct permissions.
When adding nodes to your cluster, you may need to open ports. For a listing of all ports required by ClustrixDB, including those used for multiport, please see Network Security with ClustrixDB.
If zones are in use, the newly added nodes must be assigned to their respective zone using ALTER CLUSTER ZONE. Clusters that are only partially configured for zones are not fault tolerant in the face of a zone loss.
Run this query from a SQL prompt. New node(s) are automatically assigned consecutive node number(s).
sql> SELECT * FROM system.nodeinfo ORDER BY nodeid;
You can also use The CLX Command-Line Administration Tool.
|View your cluster's status by providing the following at a bash prompt|
shell> /opt/clustrix/bin/clx status
You should see that all nodes appear OK on the display. If zones are in use, all nodes should have a non-zero zone assigned. If zones are not in use, all nodes will be assigned to zone 0.
You may notice that the data distribution amongst your nodes is not yet balanced. Be patient. It will be, soon.
If the node you are trying to add does not appear in the list above, see section below on Errors during Flex Up.
Your new node(s) have been successfully added to your ClustrixDB cluster but they do not yet contain data. The Rebalancer will now automatically work in the background to move data onto the new node(s). To monitor this process, refer to the instructions regarding Managing the Rebalancer. Your cluster is fully functional and able to be used during this process.
As part of adding nodes to your cluster, ClustrixDB performs some checks to ensure the nodes have the same configuration. This section describes errors that can be encountered with ALTER CLUSTER ADD and how to resolve those issues.
The following are errors you may encounter at the SQL prompt
|List of nodes with pending invitations|
sql> SELECT * FROM system.pending_invites;
The cluster periodically attempts to send invitations to nodes in system.pending_invites. For each invitation that is sent, there will be entries in clustrix.log:
sending invitation response(no error) to "10.2.13.68:24378"
Note: If the same node is in system.pending_invites and system.problem_nodes, you may want to remove the node from system.pending_invites before resolving the issue with system.problem_nodes. Doing this will prevent the node from being automatically added to the cluster once the problem is resolved, causing a premature group change. Instead, you may prefer to complete the node addition during off-peak hours.
|Remove a pending node addition from PENDING_INVITES|
sql> DELETE FROM system.pending_invites;
|Query system.problem_nodes to see why a node could not be added|
sql> SELECT * FROM system.problem_nodes;
Here is the list of reasons provided in system.problem_nodes and how to resolve those issues:
|Software binaries differ||Make sure all nodes are running the same version of ClustrixDB|
|Multiport settings mismatched|
See Modifying Startup Configuration Options for instructions on how to disable Multiport.
Network Security with ClustrixDB contains information relative to enabling Multiport ports.