Skip to content
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.

Memory leak when fetching addons #63

Closed
polskikiel opened this issue Dec 5, 2019 · 1 comment
Closed

Memory leak when fetching addons #63

polskikiel opened this issue Dec 5, 2019 · 1 comment
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@polskikiel
Copy link
Contributor

Description

On our long-lasting clusters, the Helm-broker sometimes restart because of the memory/goroutines leak.

Check the graphs for the Helm Broker from the nightly cluster:
image

On this cluster, we are adding addons in the loop when executing the tests, the memory leak must be related to it.

Expected result

The Helm broker has a stable memory footprint.

@polskikiel polskikiel added the kind/bug Categorizes issue or PR as related to a bug. label Dec 5, 2019
@polskikiel polskikiel added this to the Backlog_Gopher milestone Dec 5, 2019
@ksputo ksputo modified the milestones: Backlog_Gopher, Sprint_Gopher_34 Jan 9, 2020
@ksputo ksputo self-assigned this Jan 9, 2020
@mszostok
Copy link
Contributor

mszostok commented Jan 9, 2020

@a-thaler reported such issue:

When adding my URL to a fresh cluster: github.com/sap/xf-addons//addons/index.yaml
It looks like the broker just crashes with OOM

Next try to configure the URL result in:
{"level":"error","log":{"addon":"marketing-connector-0.1.0","message":"while loading addon: while getting Docs URL for addon marketing-connector: while creating archive '/tmp/docs-marketing-connector-0.1.0.tgz': file already exists: /tmp/docs-marketing-connector-0.1.0.tgz","time":"2020-01-08T14:32:34.012Z"}}

We need to check why this is not working as this is a blocker for using HB with git repo on faros pipelines.

Expected result:

  • HB recovers after OOM or any other restarts and reprocesses failed addons

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants