[Gluster-devel] posix-locks under AFR not working for server+client in one process

[Krishna Srinivas]

On Tue, Oct 14, 2008 at 9:14 PM, Rommer <rommer at active.by> wrote:
> On Tue, 14 Oct 2008 21:04:02 +0530
> "Krishna Srinivas" <krishna at zresearch.com> wrote:
>
>> Hi Rommer,
>> Can you paste the spec file of the other server too?
>> Thanks
>> Krishna
>>
>
> Config the same except for ip addresses:
>
> ####### local brick #########
> volume posix
>  type storage/posix
>  option directory /mnt/export
> end-volume
> volume posix-locks
>  type features/posix-locks
>  subvolumes posix
> end-volume
> volume io-thr
>  type performance/io-threads
>  subvolumes posix-locks
>  option thread-count 4
> end-volume
>
> #### export local brick #####
> volume server
>  type protocol/server
>  subvolumes io-thr
>  option transport-type tcp/server
>  option bind-address 192.168.1.13
>  option auth.ip.io-thr.allow 192.168.1.*
> end-volume
>
> ####### remote bricks #######
> volume remote
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host 192.168.1.12
>  option remote-subvolume io-thr
>  option transport-timeout 3
> end-volume
>
> ########### afr #############
> volume afr
>  type cluster/afr
>  subvolumes io-thr remote

Here change the order of the subvolumes. i.e as
 subvolumes remote io-thr

So that both the AFRs try to acquire the lock on the same volume.

>  option read-subvolume io-thr
> end-volume
> volume wb
>  type performance/write-behind
>  subvolumes afr
> end-volume
> volume ra
>  type performance/read-ahead
>  subvolumes wb
> end-volume
> #############################
>