[Gluster-users] several translators in the row

Roman Hlynovskiy roman.hlynovskiy at gmail.com
Thu Jul 10 09:49:57 UTC 2008


Hello everyone,

I am trying to setup a server with the following configuration:

#
# Object Storage Brick 1
#

# low-level brick pointing to physical folder
volume posix1
        type storage/posix
        option directory /mnt/os1/export
end-volume

# put support for fcntl over brick
volume locks1
        type features/posix-locks
        subvolumes posix1
        option mandatory on
end-volume

# put additional io threads for this brick
volume brick1
        type performance/io-threads
        option thread-count 4
        option cache-size 32MB # this one is per thread
        sub-volumes locks1
end-volume

#
# Object Storage Brick 2
#

# low-level brick pointing to physical folder
volume posix2
        type storage/posix
        option directory /mnt/os2/export
end-volume

# put support for fcntl over brick
volume locks2
        type features/posix-locks
        subvolumes posix2
        option mandatory on
end-volume

# put additional io threads for this brick
volume brick2
        type performance/io-threads
        option thread-count 4
        option cache-size 32MB
        sub-volumes locks2
end-volume

#
# Metadata Storage
#

volume brick-ns
        type storage/posix
        option directory /mnt/ms
end-volume

#
# Volume to export
#

volume server
        type protocol/server
        subvolumes brick1 brick2 brick-ns
        option transport-type tcp/server
        option auth.ip.brick1.allow *
        option auth.ip.brick2.allow *
        option auth.ip.brick-ns.allow *
end-volume


i.e. as recommended in best practices and tuning guides, I put locks
translator over posix brick and after that io-thread translator over
lock brick.
if I try to start the server, it gives me following errors:

Starting glusterfs server: glusterfsd.
2008-07-10 15:46:42 D [spec.y:115:new_section] libglusterfs/parser:
New node for 'posix1'
2008-07-10 15:46:42 D [spec.y:132:section_type] libglusterfs/parser:
Type:posix1:storage/posix
2008-07-10 15:46:42 D [xlator.c:104:xlator_set_type]
libglusterfs/xlator: attempt to load type storage/posix
2008-07-10 15:46:42 D [xlator.c:111:xlator_set_type]
libglusterfs/xlator: attempt to load file
/usr/lib/glusterfs/1.3.8/xlator/storage/posix.so
2008-07-10 15:46:42 D [spec.y:152:section_option] libglusterfs/parser:
Option:posix1:directory:/mnt/os1/export
2008-07-10 15:46:42 D [spec.y:216:section_end] libglusterfs/parser: end:posix1
2008-07-10 15:46:42 D [spec.y:115:new_section] libglusterfs/parser:
New node for 'locks1'
2008-07-10 15:46:42 D [spec.y:132:section_type] libglusterfs/parser:
Type:locks1:features/posix-locks
2008-07-10 15:46:42 D [xlator.c:104:xlator_set_type]
libglusterfs/xlator: attempt to load type features/posix-locks
2008-07-10 15:46:42 D [xlator.c:111:xlator_set_type]
libglusterfs/xlator: attempt to load file
/usr/lib/glusterfs/1.3.8/xlator/features/posix-locks.so
2008-07-10 15:46:42 D [xlator.c:158:xlator_set_type]
libglusterfs/xlator: dlsym(notify) on
/usr/lib/glusterfs/1.3.8/xlator/features/posix-locks.so: undefined
symbol: notify -- neglecting
2008-07-10 15:46:42 D [spec.y:201:section_sub] liglusterfs/parser:
child:locks1->posix1
2008-07-10 15:46:42 D [spec.y:152:section_option] libglusterfs/parser:
Option:locks1:mandatory:on
2008-07-10 15:46:42 D [spec.y:216:section_end] libglusterfs/parser: end:locks1
2008-07-10 15:46:42 D [spec.y:115:new_section] libglusterfs/parser:
New node for 'brick1'
2008-07-10 15:46:42 D [spec.y:132:section_type] libglusterfs/parser:
Type:brick1:performance/io-threads
2008-07-10 15:46:42 D [xlator.c:104:xlator_set_type]
libglusterfs/xlator: attempt to load type performance/io-threads
2008-07-10 15:46:42 D [xlator.c:111:xlator_set_type]
libglusterfs/xlator: attempt to load file
/usr/lib/glusterfs/1.3.8/xlator/performance/io-threads.so
2008-07-10 15:46:42 D [xlator.c:158:xlator_set_type]
libglusterfs/xlator: dlsym(notify) on
/usr/lib/glusterfs/1.3.8/xlator/performance/io-threads.so: undefined
symbol: notify -- neglecting
2008-07-10 15:46:42 D [spec.y:152:section_option] libglusterfs/parser:
Option:brick1:thread-count:4
2008-07-10 15:46:42 D [spec.y:152:section_option] libglusterfs/parser:
Option:brick1:cache-size:32MB
2008-07-10 15:46:42 E [spec.y:79:cut_tree] libglusterfs/parser:
translator tree cut
2008-07-10 15:46:42 E [spec.y:236:yyerror] libglusterfs/parser: syntax
error (text which caused syntax error: sub-volumes)
2008-07-10 15:46:42 E [spec.y:253:file_to_xlator_tree]
libglusterfs/parser: yyparser () exited with YYABORT
2008-07-10 15:46:42 E [glusterfsd.c:314:main] glusterfsd: FATAL: could
not create node graph

the server starts fine If I remove io-thread bricks at all and use
'locks bricks' as an export volumes.
Does it mean, that glustet is not able to put several translators in
the row in server configuration?

-- 
...WBR, Roman Hlynovskiy




More information about the Gluster-users mailing list