[Bugs] [Bug 1359364] New: changelog/rpc: Memory leak- rpc_clnt_t object is never freed

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1359364

            Bug ID: 1359364
           Summary: changelog/rpc: Memory leak- rpc_clnt_t object is never
                    freed
           Product: GlusterFS
           Version: 3.8.1
         Component: rpc
          Assignee: bugs at gluster.org
          Reporter: khiremat at redhat.com
                CC: bugs at gluster.org
        Depends On: 1316178, 1359363



+++ This bug was initially created as a clone of Bug #1359363 +++

+++ This bug was initially created as a clone of Bug #1316178 +++

Description of problem:
changelog rpc-clnt object is never freed and the memory is leaked.
Changelog should unref the rpc-clnt object after it's usage on DISCONNECT,
since the proper ref and unref of rpc-clnt object was not built up in rpc
layer, this was not done.

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

How reproducible:
Always

Steps to Reproduce:
1. Setup geo-replication 
2. stop and start geo-replication multiple times will leak rpc_clnt object on
brick process.


Actual results:
Memory leak

Expected results:
Process should not leak memory


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1316178
[Bug 1316178] changelog/rpc: Memory leak- rpc_clnt_t object is never freed
https://bugzilla.redhat.com/show_bug.cgi?id=1359363
[Bug 1359363] changelog/rpc: Memory leak- rpc_clnt_t object is never freed
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.