Memory leak in Jenkins SSE Gateway plugin

Description

Hi,
jenkins is terribly slow and becoming worse every day.
I tried to gain some speed by adding 4 cores to the VM through engine-phx.
It's a bit better but the real issue doesn't seem related to CPU power.
Can anybody investigate?

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA <https://www.redhat.com/>

sbonazzo@redhat.com
<https://red.ht/sig>

Attachments

1
  • 05 Dec 2018, 09:54 AM

Activity

Show:

Former user August 9, 2019 at 3:08 PM

SSE Gateway plugin upgraded to a version that is reported to fix the mem leak. Marking the ticket as resolved.

Former user July 8, 2019 at 8:28 AM

The fix should be in version 1.18 which is already deployed on Staging and expected to be rolled out to Prod.

Eyal Edri March 26, 2019 at 3:30 PM

Good news!
How do you run it on a daily basis? do you plan to add a jenkins job or cronjob ?

Former user March 26, 2019 at 1:03 PM

Jenkins was hit by the issue again today with 15800 MB used out of 16384 so I tried the workaround script attached to the upstream ticket. That helped drop memory usage to just 3532 MB which is very good news. We can install it to run on a daily basis to keep our Jenkins stable while the plugin is still not patched.

Anton Marchukov March 4, 2019 at 7:06 AM

If the reason is SSE-gateway plugin memory leak than I think having less jobs just prolongs the time between restarts unfortunately.

Eyal Edri March 4, 2019 at 6:58 AM

shouldn't this be much better now with the move of KubeVirt jobs to new Jenkins?

Galit Rosenthal March 4, 2019 at 6:55 AM

Restarted Jenkins was terrible slow

Anton Marchukov January 9, 2019 at 1:21 PM

Waiting for jenkins ssi plugin fix from u/s

Sandro Bonazzola December 5, 2018 at 11:57 AM

Yuval Turgeman can we change the OST job not to read from the jenkins the artifact?
It might overload the server which is already overloaded. can you read it from another location maybe? perhaps resources.ovirt.org?

Same reason as above, builds from jenkins of oVirt Node are not published automatically to resources.ovirt.org and ISO repo is completely missing for 4.2 branch: https://resources.ovirt.org/pub/ovirt-4.2-snapshot/
Same tracker as above, #OVIRT-2355

Sandro Bonazzola December 5, 2018 at 11:54 AM

@sbonazzo its possible that bots are downloading ISOs from Jenkins using the link on https://www.ovirt.org/node/#ovirt-node-master.

 

Can we update the link to point to official releases on resources.ovirt.org rather than the Jenkins master which is overloaded?

Sadly no. we can't link to resource.ovirt.org because node images are not published there and the ISO repository is broken. Issue is tracked here: https://ovirt-jira.atlassian.net/browse/OVIRT-2355 opened 5 months ago.

Fixed

Details

Assignee

Reporter

Priority

Created November 23, 2018 at 9:09 AM
Updated August 29, 2019 at 2:12 PM
Resolved August 9, 2019 at 3:08 PM

Flag notifications