<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>Hi,<br></div><div><br></div><span id="zwchr" data-marker="__DIVIDER__">----- Le 12 Déc 16, à 13:54, Shirly Radco <sradco@redhat.com> a écrit :<br></span><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div dir="ltr"><span style="font-size:12.8px">Hi Baptiste,</span><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Thank you very much for your reply.</span><br></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">I understand that you updated your DWH to collect every 60 seconds instead of 20.</span></div><div><span style="font-size:12.8px">I'm the oVirt DWH maintainer and </span><span style="font-size:12.8px">I would really appreciate if you can share what led you to this decision?</span><span style="font-size:12.8px"> </span></div><div><span style="font-size:12.8px">And some details on your setup.</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Do you have it installed on the same machine as the engine or on a remote one? </span></div><div><span style="font-size:12.8px">Is your database remote or local?</span></div><div><span style="font-size:12.8px">What is the scale of you environment ? Number of hosts/vms...</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">This will may help us with the bug Roy mentioned.</span></div><div><span style="font-size:12.8px"><br></span></div></div></blockquote>From my mind, it was the ovirt_engine_history DB, i don't remember if there was one or more tables that reported a lot of disk space usage. A full vacuum corrected this size issue.<br></div><div data-marker="__QUOTED_TEXT__"><div>For the bugzilla mentioned, i saw it and i applied the sampling suggestion to see if the DB grows more slowly. </div><div><br data-mce-bogus="1"></div><div>For our environment we have today (and growing)<br></div><div>* 4 DC<br data-mce-bogus="1"></div><div>* 5 Clusters<br data-mce-bogus="1"></div><div>* 9 Storages domains (iscsi)<br data-mce-bogus="1"></div><div>* About 360 virtual disks in storage domains<br data-mce-bogus="1"></div><div>* 13 Hosts (growing)<br data-mce-bogus="1"></div><div>* About 250 VMs (growing)<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>* The engine + DWH + DB server are all on the same server (hosted engine)<br data-mce-bogus="1"></div><div>* DB Size is about 3.2 GB (after the vacuum)<br data-mce-bogus="1"></div><div>* As all was on the same box, the engine setup via appliance was preferred and it was not possible to customize the size of the appliance at install/update, we wanted to keep the DB size as small as possible, but with some history. I saw that the engine appliance size will be customizable soon, so we will maybe extend the engine disk at update and keep a little bit more history or decrease the sampling interval again.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div>Have a nice day.</div><div data-marker="__QUOTED_TEXT__"><br data-mce-bogus="1"></div><div data-marker="__QUOTED_TEXT__">Regards.<br><div><br data-mce-bogus="1"></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><pre style="white-space:pre-wrap;color:rgb(80,0,80)"><span style="font-family:arial,helvetica,sans-serif;font-size:12.8px">Best regards,</span></pre><pre style="white-space:pre-wrap;color:rgb(80,0,80)"><span style="font-family:arial,helvetica,sans-serif;font-size:12.8px">Shirly Radco</span></pre><pre style="white-space:pre-wrap;color:rgb(80,0,80)"><span style="font-family:arial,helvetica,sans-serif">BI Software Engineer
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109</span></pre></div></div></div></div></div></div></div></div></div><br><div class="gmail_quote">On Thu, Dec 8, 2016 at 5:01 PM, Baptiste Agasse <span dir="ltr"><<a href="mailto:baptiste.agasse@lyra-network.com" target="_blank">baptiste.agasse@lyra-network.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:#000000"><br><br><div><span id="m_-3923956886864290678zwchr">----- Le 8 Déc 16, à 15:18, Roy Golan <<a href="mailto:rgolan@redhat.com" target="_blank">rgolan@redhat.com</a>> a écrit :<br></span></div><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><div><div class="h5"><div dir="ltr"><div><div><div><div><div><div>Hi all,<br><br></div>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.<br><br></div>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):<br><br><span style="font-family:monospace,monospace">INFO: vacuuming "pg_catalog.pg_ts_template"<br>INFO: index "pg_ts_template_tmplname_index" now contains 5 row versions in 2 pages<br>DETAIL: 0 index row versions were removed.<br>0 index pages have been deleted, 0 are currently reusable.<br>CPU 0.00s/0.00u sec elapsed 0.00 sec.<br></span><br><br></div>1. sudo su - postgres -c "psql engine -c 'vacuum verbose'" &> /tmp/vacuum.log<br><br></div>2. review the /tmp/vacuum.log<br><br></div>3. paste it to <a href="http://paste.fedoraproject.org/" target="_blank">http://paste.fedoraproject.org/</a> and reply with the link here<br><br><br>[1] <a href="http://lists.ovirt.org/pipermail/devel/2016-December/014484.html" target="_blank">http://lists.ovirt.org/pipermail/devel/2016-December/014484.html</a><br><br><br></div><div>Thanks,<br></div><div>Roy<br></div></div><br></div></div>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br><a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br></blockquote></div><br><div><a href="http://paste.fedoraproject.org/501769/48120789/" target="_blank">http://paste.fedoraproject.org/501769/48120789/</a><br data-mce-bogus="1"></div><br><div>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).<br></div><br><div>Have a nice day.<br></div><br><div>Regards.<span class="HOEnZb"><span style="color: #888888;" data-mce-style="color: #888888;" color="#888888"><br></span></span></div><span class="HOEnZb"><span style="color: #888888;" data-mce-style="color: #888888;" color="#888888"><br><div>-- <br></div><div>Baptiste<br><br></div></span></span></div></div><br>_______________________________________________<br>
Users mailing list<br><a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br><a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br><br></blockquote></div></div><br></blockquote></div><br><div data-marker="__SIG_POST__">-- <br></div><div>Baptiste</div></div></body></html>