Created attachment 1509774 [details]
pmap output from Samba PID
Description of problem:
Very high memory usage on all SMB PIDs
Version-Release number of selected component (if applicable):
Happens overtime, especially when a lot of write operations are occurring on the node via SMB
Steps to Reproduce:
1.Multiple clients connect to SMB share(s)
2.Copy multiple large files to shares
3.Check PID usage through htop or top
4.Analyse memory allocation via pmap
Over 36GB of memory consumed by one PID
Much lower memory footprint per PID
After some analysis of the SMBD process, the Samba team have said that the core SMB process is only using around 3MB of memory. So something in the gluster VFS must be consuming this excess amount of memory.
Any help you could provide would be much appreciated. Please let me know if you need any data.
Created attachment 1514324 [details]
'smbcontrol 98757 pool-usage' output
Created attachment 1514325 [details]
'strace -ttT -f -o /tmp/control.strace smbcontrol 98757 pool-usage' output
After some internal testing, we've found this issue is easily repeatable over time.
Running the Python script (Attached) over the weekend, we got the SMBD thread up to 12GB of memory usage.
I've also uploaded out test results in PDF form.
Any advice would be much appreciated,
Created attachment 1515041 [details]
VFS write test results
Created attachment 1515042 [details]
Python file for replicating issue
Just need to change line 6 to point to a VFS share.
This was tested on Windows Server 2016.
Test will run until manually stopped.
Due to lack of responses and discoveries found during testing, I'm closing this ticket and have opened another (1663519)
*** This bug has been marked as a duplicate of bug 1663519 ***