Newbie Setup Questions
rodlabs
using some Xen instances, Debian, and MogileFS.
This POC is setup in the following way using the DomU's:
2 Tracker Nodes: (Tracker 1&2; one with the primary DB, lets on
tracker1)
3 Storage Nodes: (Storage 1,2,&3)
I have set them via a deployment scripts, part of my scripts look like
the following:
#!/bin/bash
apt-get update
apt-get -y upgrade
# install some basic packages
apt-get -y install vim less unzip subversion
# install MogileFS required packages
apt-get -fqqy install build-essential libsys-syscall-perl libbsd-
resource-perl libwww-perl libgearman-client-async-perl gearman-server
libio-stringy-perl libnet-netmask-perl libio-aio-perl
## Download, Compile, and Install MogileFS code Manually
# Setup MogileFS Source Dir
mkdir -p /opt/mogilefs/src/
cd /opt/mogilefs/src/
svn export http://code.sixapart.com/svn/perlbal/tags/Perlbal-1.73/
svn export http://code.sixapart.com/svn/mogilefs/tags/mogilefs-server-2.32/
svn export http://code.sixapart.com/svn/mogilefs/tags/MogileFS-Utils-2.14/
svn export http://code.sixapart.com/svn/mogilefs/tags/MogileFS-Client-1.09/
cd /opt/mogilefs/src/Perlbal-1.73 && perl ./Makefile.PL && make &&
make install
cd /opt/mogilefs/src/mogilefs-server-2.32 && perl ./Makefile.PL &&
make && make install
cd /opt/mogilefs/src/MogileFS-Client-1.09 && perl ./Makefile.PL &&
make && make install
cd /opt/mogilefs/src/MogileFS-Utils-2.14 && perl ./Makefile.PL && make
&& make install
Questions:
1. Does this look write to you? Is there any packages that I am
missing?
2. The above method is all manual, however upon I did notice that
each of these files have a /debian dir that I can build a .deb package
out of using the deb build tools. Before I followed the above method I
did try, and was successful, in building Debian packages using the svn
co from trunk and the build scripts you guys setup. However when I
built the debs they still had a version of 1.0X. Since I had
originally checked out the code for from trunk I did my best to go
through the code to look at the version numbers in various perl libs
and found that for the most part everything matched up with the latest
versions of the code, again this is checking it out of trunk.
However, like I stated, when I built everything the packages still
said 1.00.. I went head and modified the changelog via debchange tool
and set the changelog info to latest version number but I wanted to
double check if this is correct thing to do?
3. Next on to config files: Silly questions but important:
3.a Do the tracker nodes only need the following config files:
- mogilefd.conf ( the Tracker Conf File)
- mogilefs.conf ( the mogadm tool conf file)
- mogtool.conf ( the mogtool conf file)
* I don't see needing mogadm or mogtool on the storage nodes if they
don't have tracker code on them. Is this a correct assumption?
3.b Do the storage nodes only need this conf file?
- mogstored.conf (same as above question)
4. Usage Question: Like I said so I get the system up and I begin to
use it. I inject a small file "mogtool inject /etc/hosts hosts"
everything pans out, system says great! Then I do a "mogtool list"
and it says #0 files, I turn around and do a "mogtool locate hosts"
and it gives me the paths. Any clues? Why does mogtool list not give
me the list of keys back? What background process, if any, control
this?
5. Next I try to insert bigger files and the system give me 3 second
timeouts. This is for >=64MB and =>GB files
5.a could use of my DomU's be the problem, do you think the system is
competing for resources or is this issue more a config thing?
Hope these questions are clear... looking to get past newbie :)
thanks.
-JRod
dormando
> Questions:
> 1. Does this look write to you? Is there any packages that I am
> missing?
Close enough? It seems to work for you.
> 2. The above method is all manual, however upon I did notice that
> each of these files have a /debian dir that I can build a .deb package
> out of using the deb build tools. Before I followed the above method I
> did try, and was successful, in building Debian packages using the svn
> co from trunk and the build scripts you guys setup. However when I
> built the debs they still had a version of 1.0X. Since I had
> originally checked out the code for from trunk I did my best to go
> through the code to look at the version numbers in various perl libs
> and found that for the most part everything matched up with the latest
> versions of the code, again this is checking it out of trunk.
> However, like I stated, when I built everything the packages still
> said 1.00.. I went head and modified the changelog via debchange tool
> and set the changelog info to latest version number but I wanted to
> double check if this is correct thing to do?
I'll admit I don't build these often. I can't see the harm in it though?
> 3.b Do the storage nodes only need this conf file?
> - mogstored.conf (same as above question)
Trackers just need tracker config. Everything else needs a config of what
you intend to run on it.
> 4. Usage Question: Like I said so I get the system up and I begin to
> use it. I inject a small file "mogtool inject /etc/hosts hosts"
> everything pans out, system says great! Then I do a "mogtool list"
> and it says #0 files, I turn around and do a "mogtool locate hosts"
> and it gives me the paths. Any clues? Why does mogtool list not give
> me the list of keys back? What background process, if any, control
> this?
mogtool list is deceptive. That only lists "bigfiles" - use listkeys or
just try to fetch the files back.
> 5. Next I try to insert bigger files and the system give me 3 second
> timeouts. This is for >=64MB and =>GB files
> 5.a could use of my DomU's be the problem, do you think the system is
> competing for resources or is this issue more a config thing?
You should really write a small script that more closely reflects how your
app will be uploading files. mogtool does a lot more than necessary.
Also, yes, it's possible that your DomU's are too slow. If you're using
your own client you should be able to increase the client timeout.
-Dormando