Gluster users - Jun 2010 - transport.remote-port is changing on volume restart

Hello List,

I'm evaluate gluster platform as a "static file backend" for a
webserver farm.
First of all, I have to say thank you to the guys at gluster, you did an awesome
job.

But there is one really annoying thing, after each restart of a volume in the
volume-manager, i have to change the transport.remote-port in the
"client.vol" and
remount the volume on all clients.

Is there a better way to do this or is there a misconfiguration?
My client.vol looks like this:

volume 192.168.1.167-1
    type protocol/client
    option transport-type tcp
    option remote-host 192.168.1.167
    option transport.socket.nodelay on
    option transport.remote-port 10006
    option remote-subvolume brick1
end-volume

volume 192.168.1.168-1
    type protocol/client
    option transport-type tcp
    option remote-host 192.168.1.168
    option transport.socket.nodelay on
    option transport.remote-port 10006
    option remote-subvolume brick1
end-volume

volume mirror-0
    type cluster/replicate
    subvolumes 192.168.1.168-1 192.168.1.167-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 64kB
    subvolumes iocache
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

Thank you in advance,
Rafael.

Rafael Pappert wrote:
> Hello List,
> 
> I'm evaluate gluster platform as a "static file backend" for
a webserver farm.
> First of all, I have to say thank you to the guys at gluster, you did an
awesome job.
> 
> But there is one really annoying thing, after each restart of a volume in
the
> volume-manager, i have to change the transport.remote-port in the
"client.vol" and
> remount the volume on all clients.
Why is that required? Is there a specific error message that you 
encounter? If you have the client logs, that will help even more in 
figuring out the problem.