On Thu, Feb 3, 2022 at 1:50 PM Ayansh Rocks <shashank123rastogi@gmail.com> wrote:
Do I need to clean it from every host which has the hosted engine ? Sinc the other host still can see it.
No, the metadata "whiteboard" is shared. Just one copy that you removed. Once node 3 start reporting again, it will simply put new content in there. Not sure about vdsm, maybe some component (vdsm, engine) is still trying to get status of node 3. I have been away for too long, so Didi will have to pitch in. Martin Sivak
On Thu, Feb 3, 2022 at 6:02 PM Ayansh Rocks <shashank123rastogi@gmail.com> wrote:
Hi Yedidyah,
Thanks, After cleaning it from one host i am getting below error messages on /var/log/messages
Feb 3 18:01:02 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:03 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:03 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:03 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:13 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:13 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:17 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:18 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:23 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes Feb 3 18:01:23 iondelsvr14 vdsm[11893]: ERROR Malformed metadata for host 3: received 0 of 512 expected bytes
On Thu, Feb 3, 2022 at 1:04 PM Yedidyah Bar David <didi@redhat.com> wrote:
On Thu, Feb 3, 2022 at 9:11 AM Ayansh Rocks <shashank123rastogi@gmail.com> wrote:
Hi Yedidyah,
I am thinking to do below -
# hosted-engine --set-maintenance --mode=global # hosted-engine --clean-metadata --host-id=<old_host_id> --force-clean"
I hope it is safe and tested ?
It is tested, and it's "safe" as in "Does what it's designed to do".
It's definitely not "safe" as in "riskless" - if you make a mistake, you risk damage. I didn't use it myself recently, and do not remember details anymore. It's definitely not something that you are supposed to use/need casually.
It should be safe in global maintenance, the only risk is when you remove the report of a node that currently runs the engine. As other nodes might decide that the engine needs restarting.
If unsure, and if your environment is important to you (not just some
test/dev/learn thing), I warmly suggest to try this first on a test env (can be done with nested-kvm VMs, no need for physical machines for this).
That said, others on this list (and elsewhere) did use it successfully, and I recommend again to search for examples/reports/experiences.
Good luck and best regards,
Thanks
On Thu, Feb 3, 2022 at 12:17 PM Yedidyah Bar David <didi@redhat.com>
wrote:
On Thu, Feb 3, 2022 at 5:53 AM Ayansh Rocks <shashank123rastogi@gmail.com> wrote:
Hi All,
How to clean stale hosted engine from the database. I want to
remove host id=3
Perhaps by using the options '--clean_metadata' and '--host-id' of the command 'hosted-engine'. You can check documentation, list archives, etc. for details.
Good luck and best regards, -- Didi
-- Didi
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IR3SMGNMRRGEKX...