[Gluster-users] Running Gluster client/server on single process
Bryan McGuire
bmcguire at newnet66.org
Mon Jun 21 11:31:28 UTC 2010
Hello,
> Any reasons behind commenting out the above two translators?
I was having issues with speed when dealing with small files. Craig
Carl indicated that the adjustments might help.
Craig, are these adjustments still needed on 3.0.5?
Bryan
On Jun 20, 2010, at 11:19 PM, Vijay Bellur wrote:
> On Monday 21 June 2010 06:26 AM, Bryan McGuire wrote:
>>
>> I have done the following in order to test with 3.0.5 release
>> candidate. Please correct me if I am wrong.
>>
>> Unmounted storage on both servers.
>> Stopped glusterfsd.
>> Downloaded glusterfs-3.0.5rc6.tar.gz from http://ftp.gluster.com/pub/gluster/glusterfs/qa-releases/
>> Extracted
>> ./configure
>> make
>> make install
>> Started glusterfsd
>> mounted storage on both servers.
>
> Your installation does look right.
<<<<glusterfsd.vol>>>>
## file auto generated by /bin/glusterfs-volgen (export.vol)
# Cmd line:
# $ /bin/glusterfs-volgen --name repstore1 --raid 1 192.168.1.15:/fs
192.168.1.16:/fs
volume posix1
type storage/posix
option directory /fs/gluster
end-volume
volume locks1
type features/locks
subvolumes posix1
end-volume
volume brick1
type performance/io-threads
option thread-count 8
subvolumes locks1
end-volume
volume server-tcp
type protocol/server
option transport-type tcp
option auth.addr.brick1.allow *
option transport.socket.listen-port 6996
option transport.socket.nodelay on
subvolumes brick1
end-volume
<<<<glusterfs.vol>>>>
## file auto generated by /bin/glusterfs-volgen (mount.vol)
# Cmd line:
# $ /bin/glusterfs-volgen --name repstore1 --raid 1 192.168.1.15:/fs
192.168.1.16:/fs
# RAID 1
# TRANSPORT-TYPE tcp
volume 192.168.1.16-1
type protocol/client
option transport-type tcp
option remote-host 192.168.1.16
option transport.socket.nodelay on
option transport.remote-port 6996
option remote-subvolume brick1
end-volume
volume 192.168.1.15-1
type protocol/client
option transport-type tcp
option remote-host 192.168.1.15
option transport.socket.nodelay on
option transport.remote-port 6996
option remote-subvolume brick1
end-volume
volume mirror-0
type cluster/replicate
subvolumes 192.168.1.15-1 192.168.1.16-1
end-volume
#volume readahead
# type performance/read-ahead
# option page-count 4
# subvolumes mirror-0
#end-volume
#volume iocache
# type performance/io-cache
# option cache-size `echo $(( $(grep 'MemTotal' /proc/meminfo | sed
's/[^0-9]//g') / 5120 ))`MB
# option cache-timeout 1
# subvolumes readahead
#end-volume
volume quickread
type performance/quick-read
option cache-timeout 1
option max-file-size 1024kB
# subvolumes iocache
subvolumes mirror-0
end-volume
volume writebehind
type performance/write-behind
option cache-size 4MB
subvolumes quickread
end-volume
volume statprefetch
type performance/stat-prefetch
subvolumes writebehind
end-volume
>
>>
>
> The configuration files do look fine.
> Any reasons behind commenting out the above two translators?
>
> Regards,
> Vijay
More information about the Gluster-users
mailing list