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 DaveBrosius: http://wiki.apache.org/cassandra/MultinodeCluster?action=diff&rev1=11&rev2=12 Comment: remove spam from [email protected] The default cassandra.yaml uses the local, loopback address as its listen (inter-node) and Thrift (client access) addresses: {{{ - listen_address: http://www.angosso.net/ + listen_address: locahost - rpc_address: angosso.net + rpc_address: localhost }}} - As the listen address is 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 207.46.31.61, you would change the listen address like so: + As the listen address is 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: {{{ - listen_address: 207.46.31.61 + listen_address: 192.168.1.1 }}} The Thrift interface can be configured using either a specified address, like the listen address, or using the wildcard 0.0.0.0, which causes cassandra to listen for clients on all available interfaces. Update it as either: {{{ - rpc_address: 207.46.31.61 + rpc_address: 192.168.1.1 }}} - Or perhaps this machine has a second NIC with ip 65.55.39.12 and so you split the traffic for the intra-cluster network traffic from the thrift traffic for better performance: + Or perhaps this machine has a second NIC with ip 10.140.179.1 and so you split the traffic for the intra-cluster network traffic from the thrift traffic for better performance: {{{ - rpc_address: 65.55.39.12 + rpc_address: 10.140.179.1 }}} 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: @@ -46, +46 @@ {{{ seeds: - - 207.46.31.61 + - 192.168.1.1 }}} - Once these changes are made, simply restart cassandra on this node. Use netstat to verify cassandra is listening on the right address. Look for a line like this: + Once these changes are made, simply restart cassandra on this node. Use netstat (e.g. `netstat -ant | grep 7000`) to verify cassandra is listening on the right address. Look for a line like this: - {{{tcp4 0 0 207.46.31.61.7000 *angosso.net* LISTEN}}} + {{{tcp4 0 0 192.168.1.1.7000 *.* LISTEN}}} If netstat still shows cassandra listening on 127.0.0.1.7000, then either the previous cassandra process was not properly killed or you are not editing the cassandra.yaml file cassandra is actually using. @@ -65, +65 @@ auto_bootstrap: true }}} - The second 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 207.46.31.62, set its listen address with: + The second 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.1, set its listen address with: {{{ - listen_address: 207.46.31.62 + listen_address: 192.168.2.1 }}} Finally, update the the Thrift address to accept client connections, as with the first node, either with a specific address or the wildcard: {{{ - rpc_address: 207.46.31.62 + rpc_address: 192.168.2.1 }}} Or: {{{ - rpc_address: 65.55.39.13 + rpc_address: 10.140.180.1 }}} 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.
