summaryrefslogtreecommitdiffstats
path: root/scalability/README
diff options
context:
space:
mode:
authorRahul C S <rahulcs@redhat.com>2012-02-17 17:44:37 +0530
committerRahul C S <rahulcs@redhat.com>2012-02-20 12:22:34 +0530
commit160b798aad17c48e2bf93811dd06de168244a4e1 (patch)
treeb455f3d6edf0fe33a101269b48fef3812c188cfe /scalability/README
parent58c7ab800444f2b80039d71509c5dc81a3598ead (diff)
Scalability using iozone
Change-Id: I111eb271116ce36dafd121fa7cee176539623eea Signed-off-by: Rahul C S <rahulcs@redhat.com>
Diffstat (limited to 'scalability/README')
-rw-r--r--scalability/README40
1 files changed, 40 insertions, 0 deletions
diff --git a/scalability/README b/scalability/README
new file mode 100644
index 0000000..2828682
--- /dev/null
+++ b/scalability/README
@@ -0,0 +1,40 @@
+Clustered mode iozone setup:
+----------------------------
+Before continuing reading, please make sure the iozone version is greater
+than 3.394 to run iozone in clustered mode.
+
+Iozone needs either passwordless rsh or passwordless ssh to be setup to run in
+clustered mode.
+By default, iozone uses rsh. To force iozone to use ssh, the shell variable RSH
+needs to be set to 'ssh'. The command line listed earlier uses this feature.
+
+Contents of the iconf file used [ iozone cluster mode configuration file]:
+fusion1 /mnt/fioperf /usr/bin/iozone
+fusion1 /mnt/fioperf /usr/bin/iozone
+fusion2 /mnt/fioperf /usr/bin/iozone
+fusion2 /mnt/fioperf /usr/bin/iozone
+fusion3 /mnt/fioperf /usr/bin/iozone
+fusion3 /mnt/fioperf /usr/bin/iozone
+fusion4 /mnt/fioperf /usr/bin/iozone
+fusion4 /mnt/fioperf /usr/bin/iozone
+fusion5 /mnt/fioperf /usr/bin/iozone
+fusion5 /mnt/fioperf /usr/bin/iozone
+
+[Note that each entry is repeated twice so that two child processes
+could be run on each system.]
+
+Pitfalls:
+
+1.When the config file uses IP addresses instead of hostnames,
+iozone fails to proceed. For a successful iozone run in clustered mode,
+one needs to populate the config file with hostnames.
+For name resolution, one could use /etc/hosts.
+
+2.Even after successfully configuring passwordless rsh/ssh,
+if you are unable to run iozone, make sure you flush firewall rules
+
+To look at the configured firewall rules, one could use:
+# iptables -L
+
+To flush the rules, once could use:
+# iptables -F \ No newline at end of file