Rash, for glusterfs-1.3.12 you've to * load booster xlator server side. * on client side LD_PRELOAD glusterfs-booster.so before running the application that wants to make use of booster. Booster configuration I mentioned in my previous mail is not true with glusterfs-1.3.12. On 11/7/08, Rash <rash at konto.pl> wrote: > > czw, 06 lis 2008, 22:52:15 +0400, Raghavendra G napisa?(a): > > > Ignore my previous mail. What I told is true about > > glusterfs--mainline--3.0 not with glusterfs--mainline--2.5. > > > So I should not LD_PRELOAD booster library? I'm trying to run it on > server side, where the simplest configuration is: > > > volume posix > type storage/posix > option directory /home/export > end-volume > > volume brick > > type performance/booster > > subvolumes posix > end-volume > > volume server > type protocol/server > option transport-type tcp/server > subvolumes brick > option auth.ip.brick.allow * > end-volume > > > I'm starting server with command: > > LD_PRELOAD=/opt/glusterfs-1.3.12/lib/glusterfs/glusterfs-booster.so > /opt/glusterfs-1.3.12/sbin/glusterfsd -f > /opt/glusterfs-1.3.12/etc/glusterfs/glusterfs-server.vol -L DEBUG > > and getting error cited in previous message. > > When I don't LD_PRELOAD, so server is starting, but in log file I don't > see any use of booster and performance isn't better. > > > Regards. > > -- > rash at konto pl > -- Raghavendra G -------------- next part -------------- An HTML attachment was scrubbed... URL: http://zresearch.com/pipermail/gluster-users/attachments/20081107/2cc5cd0d/attachment.htm
