On February 25, 2020 9:05:42 AM GMT+02:00, Yedidyah Bar David <didi@redhat.com> wrote:
>On Mon, Feb 24, 2020 at 4:39 PM Gianluca Cecchi
><gianluca.cecchi@gmail.com> wrote:
>>
[snip]
>> On engine I see that during these moments the postmaster process
>related to ovirt_engine_history database is 100% cpu consuming.
>> Almost every minor update I run vacuum but I don't know if there is
>something else involved.
>> Is there any bug open with in in 4.3.8?
It seems this particular problem is only on the RHV env and not in oVirt one.
Already opened a case for it. Le's see how it goes.
The main difference between the RHV one and the oVirt one is that the RHV one is hosted engine, while in the oVirt one the manager is a vm of a vSphere infra.
I don't know if this in general has a greater impact on ovirt_engine_history database.
Tried also to put in global maintenance and restart the engine vm, but the postmaster process related to ovirt_engine_history (that curiouslly took the same pid as before) keeps getting 100% of cpu, not all the time, but for some extended periods. I will monitor it
>> Is there any option to set another page as the landing one when I
>open web admin portal?
>
>I am not aware of one, but there is a very simple workaround: Keep a
>bookmark in your browser to wherever you want, and after login just
>press it. I think it should work after a few seconds, even if the
>dashboard still didn't finish loading.
You can directly access the bookmark and it will prompt you for login and then directly take you to the page.
I'm using this to directly go to the VM page on admin portal.
Thanks for suggestions.
The problems was almost solved clearing all the cookies related to the webadmin url, esepcially on firefox.
Now it takes about 30-40 seconds to get the dashboard.
Gianluca