c47408e896
This is (arguably) a hack to work around a bug in libvirt which is not well behaved wrt to using TCP ports in the unreserved space between 49152-65535. (See RFC 6335) Normally glusterd starts and binds to the first available port in range, usually 49152. libvirt's live migration also tries to use ports in this range, but has no fallback to use (an)other port(s) when the one it wants is already in use. Change-Id: Id8fe35c08b6ce4f268d46804bbb6dddab7a6b7bb BUG: 1018178 Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com> Reviewed-on: http://review.gluster.org/6210 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Anand Avati <avati@redhat.com>
10 lines
305 B
Plaintext
10 lines
305 B
Plaintext
volume management
|
|
type mgmt/glusterd
|
|
option working-directory /var/lib/glusterd
|
|
option transport-type socket,rdma
|
|
option transport.socket.keepalive-time 10
|
|
option transport.socket.keepalive-interval 2
|
|
option transport.socket.read-fail-log off
|
|
# option base-port 49152
|
|
end-volume
|