DataStax provides Debian and RedHat packaged releases for Brisk. rpm and dpkg packages are currently supported through the yum and apt package management tools.
Note
The rpm packaged releases install OpenJDK instead of Sun JDK. Debian packaged releases install Sun JDK. After you install a packaged release, DataStax recommends installing the most recently released version of the Sun JVM. Versions earlier than 1.6.0_19 are specifically not recommended.
DataStax provides yum repositories for RedHat Enterprise Linux 5 and 6 and Fedora 12, 13 and 14. These instructions assume that you have the yum package management application installed, and that you have root access on the machine where you are installing.
EPEL (Extra Packages for Enterprise Linux) contains dependent packages required by Brisk, such as jna and jpackage-utils.
Before you begin, make sure you have EPEL installed by checking for a epel.repo and epel-testing.repo in /etc/yum.repos.d.
If these EPEL repositories are not found, install the epel-release package for your OS version. For example:
rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm
You may see a warning about the RPM-GPG-KEY-EPEL key not being found. It is OK to ignore the warning. You can also obtain and install the key from the Fedora Project Web Site if you want to verify the source of the EPEL packages.
Add a yum repository file for DataStax in /etc/yum.repos.d. For example:
vi /etc/yum.repos.d/datastax.repo
In this file add the following lines where <OSType> is either EL or Fedora (depending on your operating system):
[datastax]
name= DataStax Repo for Apache Cassandra
baseurl=http://rpm.datastax.com/<OSType>/$releasever
enabled=1
gpgcheck=0
Install Brisk using yum:
yum install brisk-full
yum install brisk-demos
DataStax provides debian package repositories for Debian 6.0 (Squeeze), Debian 5.0 (Lenny), Ubuntu Lucid (10.04), and Ubuntu Maverick (10.10). These instructions assume that you have the aptitude package management application installed, and that you have root access on the machine where you are installing.
Edit the /etc/apt/sources.list file, and add the DataStax repository for your operating system. For example, where <OSType> is lenny, lucid, maverick or squeeze.
deb http://debian.datastax.com/<OSType> <OSType> main
For Debian 5.0 (Lenny), also add the following repository:
deb http://backports.debian.org/debian-backports lenny-backports main
Add the DataStax repository key to your aptitude trusted keys.
$ wget -O - http://debian.datastax.com/debian/repo_key | sudo apt-key add -
Install all Brisk packages.
$ sudo aptitude update
$ sudo aptitude install brisk-full
$ sudo aptitude install brisk-demos
The packaged releases create a user cassandra. When starting brisk as a service, the Cassandra and Hadoop tracker services run as this user. A service initialization script is located in /etc/init.d/brisk. Run levels are not set by the package.
The package installs into the following directories:
Brisk / Cassandra Directories
Hadoop Directories
Hive Directories
Hive Directories
For next steps see Initializing a Brisk Cluster and then Starting Brisk.
Binary distributions of Brisk are available from the DataStax website.
To run Brisk, you will need to install a Java Virtual Machine (JVM). DataStax recommends installing the most recently released version of the Sun JVM. Versions earlier than 1.6.0_19 are specifically not recommended.
Download the distribution to a location on your machine and unpack it:
tar -xvf brisk-1.0-beta1-bin.tar
For convenience, you may want to set the following environment variables:
export BRISK_HOME=<install_location>/brisk-<version>
export PATH=$PATH:$BRISK_HOME/bin
Create the data and logging directories needed by Brisk Cassandra. By default, Cassandra uses /var/lib/cassandra and /var/log/cassandra. To create these directories, run the following commands where $USER is the user that will run Brisk:
sudo mkdir /var/lib/cassandra
sudo mkdir /var/log/cassandra
sudo chown -R $USER:$GROUP /var/lib/cassandra
sudo chown -R $USER:$GROUP /var/log/cassandra
Brisk Directories
Installing JNA (Java Native Access) on Linux platforms can improve Brisk memory usage. With JNA installed and configured as described in this section, Linux does not swap out the JVM, and thus avoids related performance issues.
To install JNA with Brisk
$USER soft memlock unlimited $USER hard memlock unlimited
For next steps see Initializing a Brisk Cluster and then Starting Brisk.