This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2089936 - After upgrade to 6.10, Postgres database is much bigger on capsule server than the satellite server.
Summary: After upgrade to 6.10, Postgres database is much bigger on capsule server tha...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule - Content
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-24 18:23 UTC by Gourav Padholia
Modified: 2024-09-13 16:31 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 12:22:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-19863 0 None Migrated None 2024-09-13 16:31:57 UTC
Red Hat Knowledge Base (Solution) 7068008 0 None None None 2024-05-01 15:59:35 UTC

Internal Links: 2238123

Description Gourav Padholia 2022-05-24 18:23:00 UTC 
Description of problem:
Postgres database on the capsule server is double in size as compare to the Satellite server. 

Version-Release number of selected component (if applicable):
6.10

How reproducible:
Customer Environment 

Steps to Reproduce:
Satellite and Capsule upgraded from 6.9 to 6.10. 


Actual results:
/var/opt/rh/rh-postgresql12/lib/pgsql/data/base is much bigger on the size on the capsule server. 

Expected results:
/var/opt/rh/rh-postgresql12/lib/pgsql/data/base should be equal or less on the capsule server. 

Additional info:
Comment 18 Sayan Das 2023-08-30 10:25:18 UTC 
So Satellite and Capsules both are at 6.12 now and this is the current status:

Different pgsql disk space consumption while taking some actions on capsule server:

/dev/mapper/VGData-LVVarLibPgsql           72064224 38606036   29960552  57% /var/lib/pgsql  # original size
/dev/mapper/VGData-LVVarLibPgsql           72064224 38548096   30018492  57% /var/lib/pgsql  # after optimized sync
/dev/mapper/VGData-LVVarLibPgsql           72064224 52945384   15621204  78% /var/lib/pgsql  # after complete sync
/dev/mapper/VGData-LVVarLibPgsql           82381376 45831468   32632852  59% /var/lib/pgsql  # after a vacuum full


Clearly, the complete sync generates more data ( that perhaps should not be created ) and they are cleared during vacuum operation.  So a jump from 57% to 78% usage is a bit high.

Even after the vacuum, there is still a 3GiB difference from the beginning but I will ignore that part for now. ANd current pgsql disk space consumption is ~ 44 GB.


Surprisingly, The disk usage on Satellite for pgsql is only 24GiB.


dev/mapper/VGData-LVVarLibPgsql    61226828   24168656   33922276  42% /var/lib/pgsql


I am collecting the some more information from satellite and capsule , to know what sort of repos they use and what are their download policies etc But 100% this behavior\disk usage is not expected. We should not see that much of a disk space consumption difference for satellite and capsules. 

Even if we do see, It should be Satellite > Capsule but NOT Capsule > Satellite , as Satellite has three DBs in postgres.
Comment 42 Eric Helms 2024-06-06 12:22:55 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.