Bug 1145280 - EAP Patch Upload / EAP Bundle Delete Causing Disk Memory Leak
Summary: EAP Patch Upload / EAP Bundle Delete Causing Disk Memory Leak
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- Other
Version: JON 3.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ER04
: JON 3.3.0
Assignee: RHQ Project Maintainer
QA Contact: Matt Mahoney
Depends On:
Blocks: JON3-10, PRODMGT-544
TreeView+ depends on / blocked
Reported: 2014-09-22 17:57 UTC by Matt Mahoney
Modified: 2014-09-26 13:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-09-26 13:54:53 UTC
Type: Bug

Attachments (Terms of Use)
server.log (4.32 MB, text/plain)
2014-09-22 18:01 UTC, Matt Mahoney
no flags Details

Description Matt Mahoney 2014-09-22 17:57:31 UTC
Description of problem:
After Uploading an EAP Patch/Bundle, followed by an EAP Bundle Delete - JON server disk space does not get reclaimed. This has been seen via both the UI and CLI

Version-Release number of selected component (if applicable):
JON 3.3 ER03.1

How reproducible:

Steps to Reproduce:
1. On JON server, use df to get the disk utilization stats for the partition on which JON and PSQL reside.
2. From the UI, Upload an EAP patch, such as jboss-eap-6.2.3-patch.zip using Bundle Creation Wizzard.
3. Once the upload is complete, again, get the disk utilization stats using df on the JON server.
4. From the UI, delete the EAP Bundle.
5. On the JON server, get the disk utilization stats.

6. Repeate the process 2 or 3 more times.
7. Try a Vacuum operation on the RHQ database, and then get JON disk utilization stats.

Actual results:
JON server disk utilization does not decrease after deleting an EAP Bundle.

Expected results:
Disk utilization should be reclaimed after deleting an EAP Bundle.

Additional info:

Comment 1 Matt Mahoney 2014-09-22 18:01:21 UTC
Created attachment 940108 [details]

Comment 2 Lukas Krejci 2014-09-26 13:44:36 UTC
From JON perspective, things seem to work OK in my testing. When a bundle version is deleted, all associated data is deleted from the database.

This might be an issue with Postgres.

If you're able to reproduce this, could you point me to your server so that I can investigate the environment there?

Comment 3 Lukas Krejci 2014-09-26 13:54:53 UTC
Upon discussing this with other devs, this is not considered an issue because it is default (and correct) behavior of Postgres.

The data files are not shrunk by default even during vacuum, only during vacuum full.

The argument against running vacuum full during our nightly vacuum job is the fact that shrinking the files will gradually fragment them on the disk leading to (potentially great) performance degradation.

For reference:

I am closing this BZ as NOTABUG.

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