<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 02/04/2016 08:26 PM, Khoi Mai wrote:<br>
</div>
<blockquote
cite="mid:OF3BEFBD4D.4CC142DE-ON86257F4F.00515219-86257F4F.00520970@LocalDomain"
type="cite"><font face="sans-serif" size="2">Hi Gluster community,</font><br>
<br>
<font face="sans-serif" size="2">Can someone who has insight on
how rpc_client_ping_timer_expired
operates, I would love to learn more about. The reason behind
it
is that last week I had 2 fuse clients produce the same
disconnect message,
but reconnected immediately afterwards. What I'd like to know
is
what may have caused it to behave this way and where else I can
look to
build and understanding of root cause. The gluster node does
show
the same disconnect/reconnect.<br>
</font></blockquote>
<br>
The way it works is, when a first message is sent to the server,
ping rpc is sent to server and a 42 seconds timer is started by
default (It can be changed with network.ping-timeout).<br>
If the ping response comes it will stop the earlier timer
and will start a 42 second timer again for next ping message.<br>
If the ping response doesn't come in 42 seconds timer
expires at that point if there was no transport activity where some
other messages were sent/received the transport gets disconnected
and reconnect is attempted. Otherwise it think the ping response may
come after some more time so delays the timer by 42 more seconds to
see if the response comes.<br>
<br>
Pranith<br>
<blockquote
cite="mid:OF3BEFBD4D.4CC142DE-ON86257F4F.00515219-86257F4F.00520970@LocalDomain"
type="cite"><br>
<font face="sans-serif" size="2">Jan 28 14:25:27 omhq1cab
GlusterFS[1640]:
[2016-01-28 20:25:27.685703] C
[client-handshake.c:127:rpc_client_ping_timer_expired]
0-prodstatic-client-3: server 72.36.4.204:49155 has not
responded in the
last 10 seconds, disconnecting.</font><br>
<br>
<br>
<font face="sans-serif" size="2">Jan 28 14:24:52 omhq1ca9
GlusterFS[1612]:
[2016-01-28 20:24:52.589450] C
[client-handshake.c:127:rpc_client_ping_timer_expired]
0-prodstatic-client-3: server 72.36.4.204:49155 has not
responded in the
last 10 seconds, disconnecting.</font><br>
<br>
<font face="sans-serif" size="2">My setup for the volume is as
follows:
Brick4 was the one that appeared not responding to the clients.
I
have an environment where multiple clients(30+) mount this
volume
and none of them had any issues with Brick4 logged.</font><br>
<br>
<font face="sans-serif" size="2">Volume Name: prodstatic</font><br>
<font face="sans-serif" size="2">Type: Distributed-Replicate</font><br>
<font face="sans-serif" size="2">Volume ID:
187c241d-0eeb-4405-80f2-c704ea44bc36</font><br>
<font face="sans-serif" size="2">Status: Started</font><br>
<font face="sans-serif" size="2">Number of Bricks: 2 x 4 = 8</font><br>
<font face="sans-serif" size="2">Transport-type: tcp</font><br>
<font face="sans-serif" size="2">Bricks:</font><br>
<font face="sans-serif" size="2">Brick1:
server1140:/export/content/static</font><br>
<font face="sans-serif" size="2">Brick2:
server1c5d:/export/content/static</font><br>
<font face="sans-serif" size="2">Brick3:
server11ad:/export/content/static</font><br>
<font face="sans-serif" size="2"><b>Brick4:
server1781:/export/content/static</b></font><br>
<font face="sans-serif" size="2">Brick5:
server1c56:/export/content/static</font><br>
<font face="sans-serif" size="2">Brick6:
server1c58:/export/content/static</font><br>
<font face="sans-serif" size="2">Brick7:
server1c57:/export/content/static</font><br>
<font face="sans-serif" size="2">Brick8:
server1c59:/export/content/static</font><br>
<font face="sans-serif" size="2">Options Reconfigured:</font><br>
<font face="sans-serif" size="2">network.ping-timeout: 10</font><br>
<font face="sans-serif" size="2">server.allow-insecure: on</font><br>
<font face="sans-serif" size="2">features.quota: on</font><br>
<br>
<font face="sans-serif" size="2">Thanks</font><br>
<font face="sans-serif" size="2">Khoi</font><br>
<br>
<br>
**<br>
<br>
<br>
<br>
This email and any attachments may contain information that is
confidential and/or privileged for the sole use of the intended
recipient. Any use, review, disclosure, copying, distribution or
reliance by others, and any forwarding of this email or its
contents, without the express permission of the sender is strictly
prohibited by law. If you are not the intended recipient, please
contact the sender immediately, delete the e-mail and destroy all
copies.<br>
<br>
**<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</body>
</html>