[Gluster-devel] using 'option transport.socket.own-thread on'

John Smith lbalbalba at gmail.com
Fri May 31 19:13:17 UTC 2013


Hi,


As mentioned on IRC : http://irclog.perlgeek.de/gluster/2013-05-30#i_7134549


I solved this by adding a script that modifies the vol file to this
dir '/usr/lib*/glusterfs/$VERSION/filter' , which is be invoked any
time a volfile is rewritten, with the path to the volfile as an
argument to the script.


Thanks,


John Smith

On Thu, May 30, 2013 at 7:25 PM, John Smith <lbalbalba at gmail.com> wrote:
> Hi,
>
>
> Im trying to run the prove test suite with setting 'option
> transport.socket.own-thread on' for each vol file. Ive added a
> function to include.rc that adds that to each vol file, and then
> modified the individual tests to call that function after each 'volume
> create' in the tests *.t files.
>
> It looks like this :
>
> function enable-multi-thread-vol ()
> {
> $CLI volume stop $V0 force >/dev/null 2>&1
> service glusterd stop >/dev/null 2>&1
> sync
> find /var/lib/glusterd/ -name \*.vol | xargs sed -i 's/.*type
> protocol.*/&\n    option transport.socket.own-thread on/'
> service glusterd start >/dev/null 2>&1
> $CLI volume start $V0 force >/dev/null 2>&1
> }
>
> So I stop the volume, stop glusterd services, modify the files, and
> then restart glusterd and the volumes after each 'volume create'.
>
> However, the modification 'option transport.socket.own-thread on'
> doesnt always get added to the vol files.
>
> I have no idea why this is not working. Any help would be appreciated.
>
>
> Thanks,
>
>
> Regards,
>
>
> John Smith




More information about the Gluster-devel mailing list