{"id":944,"date":"2011-06-16T11:00:52","date_gmt":"2011-06-16T16:00:52","guid":{"rendered":"http:\/\/www.migrate2cloud.com\/blog\/?p=944"},"modified":"2016-03-21T02:49:20","modified_gmt":"2016-03-21T07:49:20","slug":"cassandra-cluster-with-cassandra-7-x-and-ubuntu-10-04","status":"publish","type":"post","link":"https:\/\/www.migrate2cloud.com\/blog\/cassandra-cluster-with-cassandra-7-x-and-ubuntu-10-04\/","title":{"rendered":"Cassandra Cluster on AWS EC2 with Cassandra 7.x and ubuntu 10.04"},"content":{"rendered":"

Cassandra is a highly scalable, eventually consistent, distributed, structured key-value store. Cassandra brings together\u00a0 Dynamo’s<\/a> fully distributed design \u00a0and Bigtable’s<\/a> ColumnFamily-based data model.<\/p>\n

In a cluster, Cassandra nodes exchange information about one another using a mechanism called Gossip. The nodes in a cluster needs to know one another.\u00a0 Nodes named \u201cseed\u201ds are the centre of this communication mechanism. It’s customary to pick a small number of relatively stable nodes to serve as your seeds. Do make sure that each seed also knows of at least one other. Having two nodes is what is preferred.<\/p>\n

Lets have a look at how we can bring a Cassandra cluster up with Cassandra 7.x on ubuntu 10.04<\/p>\n

First of all you have to install the java\/jdk .\u00a0 As that is out of scope for our discussion please do it on your own and let\u2019s start with cassandra.<\/p>\n

Add the following repositories to your apt sources list<\/p>\n

vim \/etc\/apt\/sources.list.d\/cassandra.list<\/p>\n

[bash]deb http:\/\/www.apache.org\/dist\/cassandra\/debian 07x main
\ndeb-src http:\/\/www.apache.org\/dist\/cassandra\/debian 07x main[\/bash]<\/p>\n

Import the following keys and add it to apt-key<\/p>\n

[bash]<\/p>\n

gpg –keyserver keyserver.ubuntu.com –recv-keys 4BD736A82B5C1B00<\/p>\n

gpg –export –armor 4BD736A82B5C1B00 | sudo apt-key add –<\/p>\n

gpg –keyserver keyserver.ubuntu.com –recv-keys F758CE318D77295D<\/p>\n

gpg –export –armor F758CE318D77295D | sudo apt-key add \u2013<\/p>\n

[\/bash]<\/p>\n

Execute<\/p>\n

[bash]apt-get update[\/bash]<\/p>\n

and make sure that no error is there with accessing the packages.<\/p>\n

Installing cassandra on all nodes(machines) with\u00a0 which we intend to build the cluster.<\/p>\n

[bash]apt-get install cassandra\u00a0 –yes[\/bash]<\/p>\n

Now edit the configuration file for Cassandra<\/p>\n

vim \/etc\/cassandra\/cassandra.yaml<\/p>\n

Here\u00a0 I will discuss the important directives that has to be edited for the cluster to take effect<\/p>\n

initial_token: <\/strong><\/p>\n

eg:\u00a0 initial_token:\u00a0 136112946768375385385349842972707284582<\/p>\n

This parameter determines the position of each node in the Cassandra ring. Initial token for the first seed node should be \u20180\u2019.Here is a simple Python script that helps to calculate the token values.<\/p>\n

[bash]<\/p>\n

#! \/usr\/bin\/python<\/p>\n

import sys<\/p>\n

if (len(sys.argv) > 1):<\/p>\n

num=int(sys.argv[1])<\/p>\n

else:<\/p>\n

num=int(raw_input(“How many nodes are in your cluster? “))<\/p>\n

for i in range(0, num):<\/p>\n

print ‘node %d: %d’ % (i, (i*(2**127)\/num))<\/p>\n

[\/bash]<\/p>\n

executing this script will prompt you for the no. of nodes in your cluster. Then it will output the initial tokens for each node.<\/p>\n

For eg: Consider a 2 node cluster, the tokens will be<\/p>\n

node 0: 0<\/p>\n

node 1: 85070591730234615865843651857942052864<\/p>\n

auto_bootstrap:<\/strong> false<\/p>\n

You can set this to false as we are just going to start the cluster for the first time.<\/p>\n

seeds:<\/strong><\/p>\n

-< ip address ><\/strong><\/p>\n

As I told you earlier, the seeds mentioned here will control the communication between the nodes.<\/p>\n

You can give the ips of the two nodes here\u00a0 for which you assigned the first two initial tokens generated by the script above.<\/p>\n

Example:<\/p>\n

Seeds:<\/p>\n

-192.168.1.10<\/p>\n

-192.168.1.13<\/p>\n

This seed entries should be the same on all nodes of the cluster.<\/p>\n

listen_address:<\/strong><\/p>\n

&<\/strong><\/p>\n

rpc_address:<\/strong><\/p>\n

You can leave both empty.<\/p>\n

Starting\u00a0 the Cassandra<\/p>\n

For starting Cassandra you can either use an init script\/ or the command \u201ccassandra\u201d. Here I will use the second option.<\/p>\n

As Cassandra service was started during the installation some values will be stored in \/var\/lib\/cassandra\/data directory. So Before starting Cassandra follow these steps.<\/p>\n

[bash]<\/p>\n

1)\u00a0\u00a0\u00a0\u00a0\u00a0 \/etc\/init.d\/cassandra stop<\/p>\n

2)\u00a0\u00a0\u00a0\u00a0\u00a0 rm \u2013rf\u00a0 \/var\/lib\/cassandra\/data<\/p>\n

3)\u00a0\u00a0\u00a0\u00a0\u00a0 mkdir \/var\/lib\/cassandra\/data<\/p>\n

[\/bash]<\/p>\n

After doing these steps on all the nodes please run the following\u00a0 command to start Cassandra on each node starting from the seed node 1<\/p>\n

[bash]# cassandra &[\/bash]<\/p>\n

After starting Cassandra on all the nodes you can check the cluster status using the following command<\/p>\n

[bash]nodetool -h <ip of the node > \u00a0-p 8080 ring[\/bash]<\/p>\n

or<\/p>\n

[bash]nodetool -h localhost -p 8080 ring[\/bash]<\/p>\n","protected":false},"excerpt":{"rendered":"

Cassandra is a highly scalable, eventually consistent, distributed, structured key-value store. Cassandra brings together\u00a0 Dynamo’s fully distributed design \u00a0and Bigtable’s ColumnFamily-based data model. In a cluster, Cassandra nodes exchange information about one another using a mechanism called Gossip. The nodes in a cluster needs to know one another.\u00a0 Nodes named \u201cseed\u201ds are the centre of […]<\/p>\n","protected":false},"author":17,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[52,34,51,3],"tags":[4,458,88,87,91,127,460,461,459,444,86,462,263,213],"class_list":["post-944","post","type-post","status-publish","format-standard","hentry","category-amazon-ebs","category-amazon-ec2","category-amazon-web-services","category-cloud-computing","tag-amazon","tag-apache-cassandra","tag-aws-ec2","tag-cassandra","tag-cassandra-cluster","tag-cloud-computing","tag-computer-cluster","tag-dynamo","tag-fault-tolerant-computer-systems","tag-java","tag-nosql","tag-python","tag-structured-storage","tag-ubuntu"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t