Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Follow the instructions for local MUSIC installation on all the machines/VMs/hosts (referred to as a node) on which you want MUSIC installed. However, Cassandra and Zookeeper needs to be configured to run as multi-node installations (instructions below) before running them.

Cassandra:

In the cassandra.yaml file which is present in the cassa_install/conf directory in each node, set the following parameters:

cassandra.yaml
cluster_name: ‘name of cluster’
#...
num_tokens: 256
#...
seed_provider:
    - class_name: org.apache.cassandra.locator.SimpleSeedProvider
      parameters:
          - seeds:  "<public ip of first seed>, <public ip of second seed>, etc"
#...
listen_address: private ip of VM 
#...
broadcast_address: public ip of VM
#...
endpoint_snitch: GossipingPropertyFileSnitch
#...
rpc_address: <private ip> 
#...
phi_convict_threshold: 12


  • In the cassandra-rackdc.properties file, assign data center and rack names as needed if required ( This is for multi data center install).

  • Once this is done on all three nodes, you can run cassandra on each of the nodes through the cassandra bin folder with this command     

    ./cassandra

  • In the cassandra bin folder, if you run the following it will tell you the state of the cluster.       

    ./nodetool status

  • To access cassandra, one any of the nodes you can run the following and then perform CQL queries.

    ./cqlsh <private ip>

Extra Cassandra information for Authentication:

To create first user in Cassandra

  1. Edit conf/Cassandra.yaml file
authenticator: PasswordAuthenticator
authorizer: CassandraAuthorizer
  1. Restart Cassandra
  2. Login to cqlsh with default credentials
cqlsh -u cassandra -p cassandra
  1. To change default user create new user with the following command.
CREATE USER new_user WITH PASSWORD ‘new_password’ SUPERUSER;
  1. Change password for default user ‘Cassandra’ so that no one will be able to login
ALTER USER cassandra WITH PASSWORD ‘SomeLongRandomStringNoonewillthinkof’;

Provide the new user credentials to Music. Update music.properties file and uncomment or add the following:

cassandra.user=<new_user>
cassandra.password=<new_password>

To access keyspace through cqlsh, login with credentials that are passed to MUSIC while creating the keyspace.

Zookeeper:

Once zookeeper has been installed on all the nodes, modify the  zk_install_location/conf/zoo.cfg on all the nodes with the following lines:

tickTime=2000
dataDir=/opt/app/music/var/zookeeper
clientPort=2181
initLimit=5
syncLimit=2
quorumListenOnAllIPs=true
server.1=public IP of node 1:2888:3888
server.2=public IP of node 2:2888:3888
server.3=public IP of node 3:2888:3888

Create the directory /var/zookeeper in all the machines and within that create a file called myid that contains the id of the machine. The machine running node.i will contain just the number i in the file myid.

Start each of the nodes one by one from the zk_install_location/bin folder using the command:

./zkServer.sh start

On each node check the file zookeeper.out in the  zk_install_location/ bin to make sure all the machines are talking to each other and there are no errors. Note that while the machines are yet to come up there maybe error messages saying that connection has not yet been established. Clearly, this is ok.

If there are no errors, then from zk_install_location/bin simply run the following to get command line access to zookeeper.   ./zkCli.sh

Run these commands on different machines to make sure the zk nodes are syncing.

[zkshell] ls /
[zookeeper]


Next, create a new znode by running

create /zk_test my_data.


This creates a new znode and associates the string "my_data" with the node. You should see:

[zkshell] create /zk_test my_data
Created /zk_test


Issue another ls / command to see what the directory looks like:

[zkshell] ls /
[zookeeper, zk_test]

MUSIC

Create a music.properties file and place it in /opt/app/music/etc at each node. Here is a sample of the file: 

my.id=0
all.ids=0:1:2
my.public.ip=public IP of node 0
#For each node, a separate file needs to be created with its own id (between 0 and the number of nodes) and with information about its own public ip. 
all.public.ips=public IP of node 0:public IP of node 1:public IP of node 2
#######################################
# Optional current values are defaults
#######################################
#zookeeper.host=localhost
#cassandra.host=localhost
#music.ip=localhost
#debug=true
#music.rest.ip=localhost
#lock.lease.period=6000
# Cassandra Login
#cassandra.user=cassandra
#cassandra.password=cassandra
# AAF Endpoint
#aaf.endpoint.url=<aafhost>
  • Build the MUSIC.war and place it within the webapps folder of the tomcat installation.
  • Start tomcat and you should now have MUSIC running.

For Logging create a dir /opt/app/music/logs. When MUSIC/Tomcat starts a MUSIC dir with various logs will be created.

Muting MUSIC jersey output


The jersey package that MUSIC uses to parse REST calls prints out the entire header and json body by default. To mute it (if it exists), remove the following lines from the web.xml in the WEB_INF folder:


<init-param>
  <param-name>com.sun.jersey.spi.container.ContainerResponseFilters</param-name>
  <param-value>com.sun.jersey.api.container.filter.LoggingFilter</param-value>
</init-param>

  






  • No labels