<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 12/30/2012 12:31 PM, William
Muriithi wrote:
</div>
<blockquote
cite="mid:CAE9rU+7CNvbZ-Pos=BfBDUuoCU885mN8__A4amvPMnPmGQMvwQ@mail.gmail.com"
type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">For mysql, I set up my innodb store to use 4 files (I don't do 1 file
per table), each file distributes to each of the 4 replica subvolumes.
This balances the load pretty nicely.
</pre>
</blockquote>
</blockquote>
<pre wrap="">It's not so much a "how glusterfs works" question as much as it is a how
innodb works question. By configuring the innodb_data_file_path to start
with a multiple of your bricks (and carefully choosing some filenames to
ensure they're distributed evenly), records seem to be (and I only have
tested this through actual use and have no idea if this is how it's
supposed to work) accessed evenly over the distribute set.
</pre>
</blockquote>
<pre wrap="">Hmm, have you checked on the gluster servers that these four files are
in separate bricks? As far as I understand, if you have not done
anything Glusterfs scheduler (Default ALU on version 3.3), it is
likely that is not whats happening. Or you are using a version that
has a different scheduler. Interesting though. Poke around and
update us please
</pre>
</blockquote>
Not just checked, but engineered. At the time I created a file then
checked which dht subvolume it was on using "getfattr -n
trusted.glusterfs.pathinfo $file" for each file, then incremented
the filename until it was created on the subvolume I wanted.<br>
<br>
As an aside, I'm referring to DHT (distrubute) <i>subvolumes</i>
rather than bricks because AFR (replicate) is under DHT meaning that
replicate actually is the translator whose subvolumes map 1:1 to
bricks in my setup.<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</body>
</html>