[Bugs] [Bug 1268125] glusterd memory overcommit

[bugzilla at redhat.com]

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

ryanlee at zepheira.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|needinfo?(ryanlee at zepheira. |
                   |com)                        |



--- Comment #4 from ryanlee at zepheira.com ---
I've generated the statedump files and cut out 6336 sections named
xlator.features.locks.backup-locks.inode from backup.dump.  I'm hoping the
contents of the inode context and the specific names of clients aren't
necessary bits of info and have removed them from the dump files.

The cmd_history.log is pretty empty.  The memory starts leaking immediately on
start/restart.  We're currently mitigating by restarting the process once a
week, the growth rate is quite steady without having done anything else. 
cmd_history does contain successes for updating volume settings (specifically,
SSL allows) that our internal management system runs every half hour.  We could
probably stand to modify it to issue changes only if the values differ, but
that doesn't look to me to be the source of the issue.

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