Distributed Systems Project 3 Report

Abhinav Gopisetty Naga Rekha Malae Divya Dwarakanath Venkata Shravan Ponnam

Monitoring system using Pub/Sub messaging middleware. Middleware is an important class of technology that is helping to decrease the cycle-time, level of effort, and complexity as-sociated with developing high-quality, flexible, and interoperable distributed systems. A Pub/Sub Messaging system has three components: Broker, Publisher and Subscriber. Broker: The broker is the enabler. The broker’s job is to connect publishers with Subscribers. The broker contains a list of subscribers and what messages they are Interested in. The broker exposes endpoints that allow for subscribers to subscribe to messages and a publisher to publish interesting messages. Publisher: The only thing the publisher knows is that when it has anything to publish it simply sends the message to the Broker. The publisher has no idea on the final destination of the message or if there even is a final destination. This promotes a very decoupled system in that the publisher knows nothing about their subscribers. Subscriber: A subscriber communicates with the broker to tell it what published messages it is interested in. In this project we have monitored the CPU and Memory Usage of the system using the brokering system. We are using the Narada brokering systems here. And we are generating the results onto graphs to check the performance. We first check the performance of our local computer. Then we wanted to check how this would work on a distributed System. So we have tested it on Silo cluster, but we are running only on the head node on silo once the values were stabilized we ran MPI pagerank program to check the change in CPU and Memory Utilization and we have captured images of it on graphs. Then we ran our program using Eucalyptus on Virtual Machine instances and checked the Utilization. The following are the graphs that we have generated and a brief description about them:

Below are the three images for silo, when the publisher is run on the head node. In the second graph the PageRank is started approximately at 21.26.55. In the third graph the PageRank stops at 2.1.27.35. The third graph shows the events that take place after the prior two.

The below images show the results when the publisher is run on multiple VM instances. We ran our publisher on two VM instances. Notes on the publisher and consumer for VM instances. Our publisher class publishes the memory utilization and Cpu utilization (net user + Cpu) for every 100 Milli seconds. However, when the consumer is receiving this information it receives them asynchronously. We record the fist event sent by vm A and wait until event from vm B is received and then take the average of the both.

References:

1) B534 Lecture Notes 2) http://www.java2s.com/Code/Java/Chart/JFreeChartDynamicDataDemo.htm