Bug 1703007 - The telnet or something would cause high memory usage for glusterd & glusterfsd
Summary: The telnet or something would cause high memory usage for glusterd & glusterfsd
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 5
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-25 09:33 UTC by Terry Cui
Modified: 2023-09-14 05:27 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-09 05:34:35 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Terry Cui 2019-04-25 09:33:02 UTC
Description of problem:
  I'm afraid that the telnet or something would cause high memory usage for glusterd & glusterfsd.

  For example, if the script is executed for days:

  while [[ 1 ]]; do
      echo "quit" | telnet xx.xx.xx.xx 24007
      echo "quit" | telnet xx.xx.xx.xx 49152
  done
  
  Later, the memory usage for glusterd & glusterfsd would be changed from 0.5% to 2.9%.
  
  Hope someone could help me. Thanks a lot.


Version-Release number of selected component (if applicable):
GlusterFS 5.6 or below

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Atin Mukherjee 2019-04-29 03:08:35 UTC
It's not clear to me how would a telnet cause an increase in the memory consumption of glusterd process and more over what's the motivation behind this? Could you help us in providing the following by a small test:

Before and after telnet, capture statedumps of glusterd process (kill -SIGUSR1 $(pidof glusterd) and find the files in /var/run/gluster and share back here? Also do you see any logs in the glusterd and brick log files when you attempt to do telnet.

Comment 2 Atin Mukherjee 2019-05-08 04:32:42 UTC
Ping?

Comment 3 Atin Mukherjee 2019-06-09 05:34:35 UTC
Closing this as we haven't received sufficient information.

Comment 4 Red Hat Bugzilla 2023-09-14 05:27:34 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.