On 8 December 2016 at 17:01, Baptiste Agasse <baptiste.agasse@lyra-network.com> wrote:


----- Le 8 Déc 16, à 15:18, Roy Golan <rgolan@redhat.com> a écrit :
Hi all,

Following the thread about vacuum tool [1] I would like to gather some feedback about your deployment's db vacuum status The info is completely anonymous and function running it is a read only reporting one and should have little or no effect on the db.

The result can be pretty verbose  but again will not disclose sensitive info. Anyway review it before pasting it. It should look something like that(a snippet of one table):

INFO:  vacuuming "pg_catalog.pg_ts_template"
INFO:  index "pg_ts_template_tmplname_index" now contains 5 row versions in 2 pages
DETAIL:  0 index row versions were removed.
0 index pages have been deleted, 0 are currently reusable.
CPU 0.00s/0.00u sec elapsed 0.00 sec.


1. sudo su - postgres  -c "psql engine -c 'vacuum verbose'" &> /tmp/vacuum.log

2. review the /tmp/vacuum.log

3. paste it to http://paste.fedoraproject.org/ and reply with the link here


[1] http://lists.ovirt.org/pipermail/devel/2016-December/014484.html


Thanks,
Roy

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


But, we run a full vacuum about one month ago that have free about 8GB of space and we set DWH_SAMPLING=60 to decrease data size of DWH (install is ~ 1y and half old, updated from 3.5 to 3.6 to 4.0).

Have a nice day.

Regards.

--
Baptiste


Baptiste thank you very much for submitting this, very helpful.
I wonder if it was the engine or dwh db who took most of the 8gb.
FYI there is a discussion on increasing the interval to 60 on  Bug 1395608 - DWH sampling is too high