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=10&rev2=11 rpc_address: 207.46.31.61 }}} - Or: + 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: {{{ rpc_address: 65.55.39.12 @@ -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.61, 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 207.46.31.62, set its listen address with: {{{ - listen_address: 207.46.31.61 + listen_address: 207.46.31.62 }}} 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.61 + rpc_address: 207.46.31.62 }}} Or: {{{ - rpc_address: 65.55.39.12) + rpc_address: 65.55.39.13 }}} 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.
