Name* |
Enter a name for the node. Nodes names must be unique
within a datacenter. Required. |
Rack |
Enter the name of the rack. If a rack is not entered, the
rack name default is rackn. Example:
rack1. |
SSH IP Address* |
Default: SSH IP Address specified for the cluster.
Required. |
SSH Management Port |
Enter a port value if you do not want to inherit the
value from the datacenter. Default value for SSH port at the
cluster level is 22. |
SSH Credentials |
Select an SSH
credential to apply at the node level to override
inheriting the credentials from the datacenter
level. |
Config Profile |
Select a configuration file to apply at the node level,
which overrides inheriting the configuration profile from
the cluster or datacenter levels. Defaults to the datacenter
config profile. |
Listen Address |
Default: SSH IP Address. The IP address or hostname that
Cassandra binds to for connecting to other Cassandra
nodes. |
Broadcast Address |
Default: Listen Address. The broadcast address is the IP
address a node tells other nodes in the cluster to contact
it by. A broadcast address allows public and private
addresses to be different. For example, use the broadcast
address in topologies where not all nodes have access to
other nodes by their private IP addresses. |
RPC Address |
Default: SSH IP Address. |
Broadcast RPC Address |
Default: RPC Address. |
Comment |
Enter an optional comment about the node. |
Seed Node |
Select a seed node option:
- Automatically choose:
(Default) Allow Lifecycle Manager to select a seed
node. LCM designates two nodes as seeds per
datacenter.
- Make this a seed node: Select
to designate the node as a seed node used by gossip
for bootstrapping new nodes joining a cluster.
Warning: When adding
a node to an existing datacenter that has already
been converged (that is, an install job has
already been run) in LCM, a tooltip warning
appears: New nodes that list themselves as seeds
will fail to bootstrap and will require
immediately running a repair on the node. DataStax
recommends designating the node as a seed after
the node has bootstrapped into the
cluster.
- Do not make this a seed node:
Select to explicitly exclude the node from seed node
designation.
After adding a node but before running a job, the
Node Details displays the status as not a seed node. The
true seed node status is not displayed until after
running an install job.
Note: It is
a best practice to designate more than one seed node per
datacenter (ideally two per datacenter); however, do not
make all nodes seed nodes. Please read Internode
communications (gossip).
|