[Bugs] [Bug 1268125] New: glusterd memory overcommit

bugzilla at redhat.com bugzilla at redhat.com
Thu Oct 1 21:21:17 UTC 2015


            Bug ID: 1268125
           Summary: glusterd memory overcommit
           Product: GlusterFS
           Version: 3.7.4
         Component: unclassified
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: ryanlee at zepheira.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com

Description of problem:

We were using Gluster 3.3 through 3.5 without issue but needed to add SSL
support.  Due to SSL bugs in earlier versions, the quickest path forward was to
upgrade the network to 3.7.  This generally appears to be fine as files added
are appearing where they should, except that it's caused glusterd to vastly
overcommit memory on both nodes where it runs.

On one (serverA, the 'master'), it had 4GB of RAM to work with, and the other
(serverB) 2GB.  Both got up to around 30GB of committed virtual memory in a
couple of weeks. When other processes were stopped on serverA and glusterd
restarted, the overcommit problem appeared to be alleviated and, if it was
growing at all, grew a lot slower.  We had to resize serverA and took it
offline; at the same time, serverB glusterd shot up to 140GB while it was
offline.  Both are currently at 2GB of RAM (for other reasons) and, after
restarting both daemons, appear to be growing in committed memory at around

Version of GlusterFS package installed:


Location from which the packages are used:

Launchpad PPA

GlusterFS Cluster Information:

    Number of volumes: 2
    Volume Names: backup, other
    Volume on which the particular issue is seen: N/A
    Type of volumes: backup Replicate, other Distribute
    Volume options if available:

Volume Name: backup
Type: Replicate
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Brick1: serverA:/glusterfs/brick3/data
Brick2: serverB:/glusterfs/brick3/data
Options Reconfigured:
auth.ssl-allow: [names]
ssl.cipher-list: HIGH:!SSLv2
ssl.certificate-depth: 3
server.ssl: on
client.ssl: on

Volume Name: other
Type: Distribute
Status: Started
Number of Bricks: 1
Transport-type: tcp
Brick1: serverA:/glusterfs/brick4/data
Options Reconfigured:
[same as above]

    Client Information
        OS Type: Linux
        Mount type: GlusterFS

How reproducible:

Have not tried (sorry).

Steps to Reproduce:


Actual results:

Expected results:

Logs Information:

I stripped dates and did a uniq -n on the actual log messages for the glusterd
process.  server setup and SSL connect errors appear together.

  17299  E [socket.c:2863:socket_connect]
[0x7f577a62255d] ) 0-socket: invalid argument: this->private [Invalid argument]
    400  W [dict.c:1452:dict_get_with_ref]
[0x7f57813af6a2] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x19406)
[0x7f57813ad406] ) 0-dict: dict OR key (graph-check) is NULL [Invalid argument]
    217  E [socket.c:2388:socket_poller] 0-socket.management: server setup
    217  E [socket.c:352:ssl_setup_connection] 0-socket.management: SSL connect
     16  W [dict.c:1452:dict_get_with_ref]
[0x7f3c80fa96a2] -->/usr/lib/x86_64-linux-gnu/libglusterfs.so.0(+0x19406)
[0x7f3c80fa7406] ) 0-dict: dict OR key (graph-check) is NULL [Invalid argument]
     11  E [socket.c:2501:socket_poller] 0-socket.management: error in polling

Additional info: 

This is totally unrelated (probably?), but in order to get glusterd to really
start, I had to ln
/usr/lib/x86_64-linux-gnu/glusterfs/3.7.4/xlator/rpc-transport -s
/usr/lib/x86_64-linux-gnu/glusterfs/3.7.4/rpc-transport as the logs were
essentially complaining about being unable to find

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list