Hello, Yes I did find some hits on this in the following logs. We started seeing failures after upgrading to 5.3 from 4.6. If you want me to check for something else let me know. Thank you all on the gluster team for finding and fixing that problem whatever it was! [root@lonbaknode3 glusterfs]# zgrep ping_timer /var/log/glusterfs/home-volbackups* .... /var/log/glusterfs/home-volbackups.log-20190317.gz:[2019-03-16 10:34:44.419605] C [rpc-clnt-ping.c:162:rpc_clnt_ping_timer_expired] 0-volbackups-client-3: server 1.2.3.4:49153 has not responded in the last 42 seconds, disconnecting. /var/log/glusterfs/home-volbackups.log-20190317.gz:[2019-03-16 10:34:44.419672] C [rpc-clnt-ping.c:162:rpc_clnt_ping_timer_expired] 0-volbackups-client-6: server 1.2.3.4:49153 has not responded in the last 42 seconds, disconnecting. /var/log/glusterfs/home-volbackups.log-20190317.gz:[2019-03-16 10:34:57.425211] C [rpc-clnt-ping.c:162:rpc_clnt_ping_timer_expired] 0-volbackups-client-9: server 1.2.3.4:49153 has not responded in the last 42 seconds, disconnecting. /var/log/glusterfs/home-volbackups.log-20190317.gz:[2019-03-16 11:46:25.768650] C [rpc-clnt-ping.c:162:rpc_clnt_ping_timer_expired] 0-volbackups-client-6: server 1.2.3.4:49153 has not responded in the last 42 seconds, disconnecting. /var/log/glusterfs/home-volbackups.log-20190317.gz:[2019-03-16 16:02:29.921450] C [rpc-clnt-ping.c:162:rpc_clnt_ping_timer_expired] 0-volbackups-client-3: server 1.2.3.4:49153 has not responded in the last 42 seconds, disconnecting. .... ----- What was the version you saw failures in? Were there any logs matching with the pattern "ping_timer_expired" earlier? |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
