Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

logging plugin consumes large amount of memory #50

Closed
lybroman opened this issue May 7, 2019 · 3 comments
Closed

logging plugin consumes large amount of memory #50

lybroman opened this issue May 7, 2019 · 3 comments

Comments

@lybroman
Copy link

lybroman commented May 7, 2019

What happened:
logging plugin consumes large amount of memory

Mem: 5498852K used, 2148392K free, 166208K shrd, 50612K buff, 938332K cached
CPU: 63% usr 10% sys 0% nic 26% idle 0% io 0% irq 0% sirq
Load average: 1.48 1.62 1.66 2/507 8054
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
3476 3459 root S 2575m 34% 1 53% /bin/splunk-logging-plugin

What you expected to happen:
logging plugin should consume acceptable amount of memory

How to reproduce it (as minimally and precisely as possible):
It happened after enabling the plugin for some time. We have several containers using this plugin to forward the logs to splunk instance.

Environment:

  • Docker version (use docker version): 17.06.0-ce
  • OS (e.g: cat /etc/os-release): Alpine Linux v3.5
@mhoogcarspel-splunk
Copy link

I think this is same/similar to the issue ADDON-21861 that I reported internally in Splunk (with some more specific steps to repro this faster), just leaving a note here so I get updates here too, left a note on the internal issue too linking to here.

@dbaldwin-splunk
Copy link
Contributor

@gp510 Since you are tracking also.

@gp510
Copy link
Contributor

gp510 commented Jul 29, 2019

The fix for this issue has been merged to the develop branch: #53

It was being caused by calling time.NewTicker in a fast iterating loop.

Before fix:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
14845 root 20 0 709216 642488 5860 S 93.7 15.9 31:15.22 splunk-logging-

After fix:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
7570 root 20 0 108240 104824 5540 S 7.9 2.6 6:37.93 splunk-logging-

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants