If you want to make the db smaller with immediate affect, please do full vacuum and analyze after deleting the rows from the DB or waiting a day for the DWH to do this.


Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
        8272306
Email: ydary@redhat.com
IRC : ydary

On Fri, Sep 2, 2016 at 12:07 PM, <nicolas@devels.es> wrote:
I tried adjusting the DWH_TABLES_KEEP_HOURLY parameter to a very low value and also setting the DWH_SAMPLING parameter to 60 and restarted both ovirt-engine-dwhd and ovirt-engine daemons, however, the database is still huge.

So even if I change those parameters should I manually clean up the database? If so, what's the recommended way?

Thanks.


El 2016-09-01 19:26, Shirly Radco escribió:
Another option is to set the DWH_SAMPLING back to 60  and restart
dwh.
 This will lower the granularity of the dashboard calculations.
 The dwh db size grow since now it samples the statistics every 15
seconds instead of once a minute.

Best regards,
 Shirly Radco

On Sep 1, 2016 19:29, <nicolas@devels.es> wrote:

Hi Didi,

El 2016-09-01 14:02, Yedidyah Bar David escribió:
On Thu, Sep 1, 2016 at 3:26 PM, Sandro Bonazzola
<sbonazzo@redhat.com>
wrote:

Didi, Shirly, can you help here?

On Thu, Sep 1, 2016 at 8:52 AM, <nicolas@devels.es> wrote:

Hi,

Since we upgraded to 4.0.x, DWH's PostgreSQL database is getting
really huge. Is there a clean way to limit its size, like setting
a maximal retention time for DWH data?

 Earlier today replied to a similar question, search list archives for
 "Change Engine History Logging from Advanched to Basic".

 Just to confirm: I already have basic DWH configured, and the content
of /etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-scale.conf
is:

   DWH_TABLES_KEEP_SAMPLES=24
   DWH_TABLES_KEEP_HOURLY=720
   DWH_TABLES_KEEP_DAILY=0

 So according to [1] regarding "DWH_TABLES_KEEP_HOURLY":

   The number of hours that hourly data is stored. The default is 60
days.
   Hourly data more than two days old is aggregated into dailydata.

 if I reduce that value to say 240 (10 days), any older entry from
that should be erased upon a DWH restart, right?

 Thanks.

   [1]:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/pdf/Reports_and_Data_Warehouse_Guide/Red_Hat_Enterprise_Virtualization-3.6-Reports_and_Data_Warehouse_Guide-en-US.pdf
[3]

Best,

 

Thanks.
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users [1] [1]

--

Sandro Bonazzola
Better technology. Faster innovation. Powered by community
collaboration.
See how it works at redhat.com [2] [2]

[3]

 --

 Didi

 Links:
 ------
 [1] http://lists.ovirt.org/mailman/listinfo/users [1]
 [2] http://redhat.com [2]
 [3]
https://www.redhat.com/it/about/events/red-hat-open-source-day-2016
[4]


Links:
------
[1] http://lists.ovirt.org/mailman/listinfo/users
[2] http://redhat.com
[3]
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/pdf/Reports_and_Data_Warehouse_Guide/Red_Hat_Enterprise_Virtualization-3.6-Reports_and_Data_Warehouse_Guide-en-US.pdf
[4] https://www.redhat.com/it/about/events/red-hat-open-source-day-2016
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users