Configure gossip
When a node first starts up, it looks at its cassandra.yaml configuration file to determine the name of the cluster it belongs to;
which seed nodes to contact to obtain information about the other nodes in the cluster;
and other details including the messaging port and token range ownership.
In the cassandra.yaml file, set the following parameters:
| Property | Description |
|---|---|
Name of the cluster that this node is joining. Must be the same for every node in the cluster. |
|
The IP address or hostname that the Cassandra process binds to for connecting this node to other nodes. Default: |
|
Optional: |
Use this option instead of |
Optional: |
The public IP address this node uses to broadcast to other nodes outside the network or across regions in multi-region deployments.
If this property is commented out, the node uses the same IP address or hostname as A node does not need a separate |
The Java class for the seed provider, and the seeds list ( Default: [IMPORTANT] ==== Don’t make every node a seed node because it increases maintenance and reduces gossip performance. Gossip optimization isn’t critical, but DataStax recommends a small seed list with two or three seed nodes per datacenter. ==== |
|
The port nodes use to privately communicate with each other. Must be the same for every node in the cluster. Default: |
|
Optional: |
The token assigned to the node which is the first token of the range of tokens the node owns. This property is typically set for legacy clusters with single-node-per-token architecture, in which a node owns exactly one contiguous range in the ring space. |
The number of tokens assigned to this node in a cluster that uses virtual nodes (vnodes). Default: |