[Gluster-users] Change transport-type on volume from tcp to rdma, tcp

[Soumya Koduri]

 From the following errors,

[2015-07-21 14:36:30.495321] I [MSGID: 114020] [client.c:2118:notify] 
0-vol_shared-client-0: parent translators are ready, attempting connect 
on transport
[2015-07-21 14:36:30.498989] W [socket.c:923:__socket_keepalive] 
0-socket: failed to set TCP_USER_TIMEOUT 0 on socket 12, Protocole non 
disponible
[2015-07-21 14:36:30.499004] E [socket.c:3015:socket_connect] 
0-vol_shared-client-0: Failed to set keep-alive: Protocole non disponible

looks like setting TCP_USER_TIMEOUT value to 0 on the socket failed with 
error (IIUC) "Protocol not available".
Could you check if 'network.ping-timeout' is set to zero for that volume 
using 'gluster volume info'? Anyways from the code looks like 
'TCP_USER_TIMEOUT' can take value zero. Not sure why it has failed.

Niels, any thoughts?

Thanks,
Soumya

On 07/21/2015 08:15 PM, Geoffrey Letessier wrote:
> [2015-07-21 14:36:30.495321] I [MSGID: 114020] [client.c:2118:notify]
> 0-vol_shared-client-0: parent translators are ready, attempting connect
> on transport
> [2015-07-21 14:36:30.498989] W [socket.c:923:__socket_keepalive]
> 0-socket: failed to set TCP_USER_TIMEOUT 0 on socket 12, Protocole non
> disponible
> [2015-07-21 14:36:30.499004] E [socket.c:3015:socket_connect]
> 0-vol_shared-client-0: Failed to set keep-alive: Protocole non disponible