[Gluster-devel] spurious failures tests/bugs/tier/bug-1205545-CTR-and-trash-integration.t

[Krishnan Parthasarathi]

> It seems this is exactly whats happening.
> 
> I have a question, I get the following data from netstat and grep
> 
> tcp        0      0 f6be17c0fbf5:1023       f6be17c0fbf5:24007
>  ESTABLISHED 31516/glusterfsd
> tcp        0      0 f6be17c0fbf5:49152      f6be17c0fbf5:490
>  ESTABLISHED 31516/glusterfsd
> unix  3      [ ]         STREAM     CONNECTED     988353   31516/glusterfsd
>     /var/run/gluster/4878d6e905c5f6032140a00cc584df8a.socket
> 
> Here 31516 is the brick pid.
> 
> Looking at the data, line 2 is very clear, it shows connection between
> brick and glusterfs client.
> unix socket on line 3 is also clear, it is the unix socket connection that
> glusterd and brick process use for communication.
> 
> I am not able to understand line 1; which part of brick process established
> a tcp connection with glusterd using port 1023?

This is the rpc connection from any glusterfs(d) process to glusterd to fetch
volfile on receiving notification from glusterd.