Description of problem:

Log file `glustershd.log` is being filled with this error:

```
[2018-08-02 10:13:13.210769] W [rpc-clnt.c:1739:rpc_clnt_submit] 4-vol_d5fd2148f6bf0348a44506763571109e-client-2: error returned while attempting to connect to host:(null), port:0
[2018-08-02 10:13:13.211105] W [rpc-clnt.c:1739:rpc_clnt_submit] 4-vol_d5fd2148f6bf0348a44506763571109e-client-2: error returned while attempting to connect to host:(null), port:0
[2018-08-02 10:13:13.219039] W [rpc-clnt.c:1739:rpc_clnt_submit] 2-vol_d5fd2148f6bf0348a44506763571109e-client-2: error returned while attempting to connect to host:(null), port:0
[2018-08-02 10:13:13.219345] W [rpc-clnt.c:1739:rpc_clnt_submit] 2-vol_d5fd2148f6bf0348a44506763571109e-client-2: error returned while attempting to connect to host:(null), port:0
[2018-08-02 10:13:13.226175] W [rpc-clnt.c:1739:rpc_clnt_submit] 0-vol_d5fd2148f6bf0348a44506763571109e-client-2: error returned while attempting to connect to host:(null), port:0
[2018-08-02 10:13:13.226456] W [rpc-clnt.c:1739:rpc_clnt_submit] 0-vol_d5fd2148f6bf0348a44506763571109e-client-2: error returned while attempting to connect to host:(null), port:0
```

The log file size increased to 10GB within about 2 days it this is causing disk space shortage on my servers.


Version-Release number of selected component (if applicable): glusterfs 3.12.10



How reproducible:


Steps to Reproduce:

Not sure how to reproduce this.
We have a cluster of 4 nodes of glusterfs (version 4.0.2) running on Kubernetes.
The glusterfs client version is 3.12.
This happens on some nodes that have a container mounts a glusterfs volume.

Actual results:

This is causing disk space shortage on my servers.

Expected results:

How to avoid this error or at least reduce the number of errors logged?

Additional info:

According to this: https://github.com/gluster/glusterd2/issues/940#issuecomment-408038184

the errors seem to be expected behaviors, but too much logs is a problem.