On 12/30/2012 12:31 PM, William Muriithi wrote: >>>> 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. >> 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. >> > 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 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. As an aside, I'm referring to DHT (distrubute) /subvolumes/ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20121230/9a197c49/attachment.html>
