Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "MultinodeCluster" page has been changed by BenjaminBlack. http://wiki.apache.org/cassandra/MultinodeCluster -------------------------------------------------- New page: = Creating a multinode cluster = The default storage-conf.xml provided with Cassandra is great for getting up and running on a single node. However, it is inappropriate for use in a multi-node cluster. The configuration and process here are the ''simplest'' way to create a multi-node cluster, but may not be the ''best'' way in production deployments, particularly because it assumes you have no data in your first node. == Preparing the first node == The default storage-conf.xml uses the local, loopback address as its storage address: {{{<ListenAddress>localhost</ListenAddress>}}} As this is the address used for intra-cluster communication, it must be changed to a routable address so the other nodes can reach it. For example, assuming you have an Ethernet interface with address 192.168.1.1, you would change the listen address like so: {{{<ListenAddress>192.168.1.1</ListenAddress>}}} If the DNS entry for your host is correct, it is safe to use a hostname instead of an IP address. Similarly, the seed information should be changed from the loopback address: {{{ <Seeds> <Seed>127.0.0.1</Seed> </Seeds> }}} Becomes: {{{ <Seeds> <Seed>192.168.1.1</Seed> </Seeds> }}} Once these changes are made, simply restart cassandra on this node. Use netstat to verify cassandra is listening. Look for a line like this: {{{tcp4 0 0 192.168.1.1.7000 *.* LISTEN}}} == Preparing the rest of the nodes == The other nodes in the ring will use a storage-conf.xml almost identical to the one on your first node. The first change is to turn on automatic bootstrapping. This will cause the node to join the ring and attempt to take control of a range of the token space: {{{<AutoBootstrap>true</AutoBootstrap>}}} The other change is to the listen address, as it must also not be the loopback and cannot be the same as any other node. Assuming your second node has an Ethernet interface with the address 192.168.2.34, set its listen address with: {{{<ListenAddress>192.168.1.1</ListenAddress>}}} Note that you should leave the Seeds section of the configuration as is so the new nodes know to use the first node for bootstrapping. Once these changes are made, start cassandra on the new node and it will automatically join the ring, assign itself an initial token, and prepare itself to handle requests.
