Clear the Servers List

162 views
Skip to first unread message

Lylian b

unread,
Jul 18, 2019, 3:13:06 AM7/18/19
to Opencast Users
Hi all !

We finished to configure all nodes on our opencast system. As you can see on the capture :


The server who are offline are unused now. How can i clear these offline servers from the list ?

Best regards,

Lylian.

Greg Logan

unread,
Jul 22, 2019, 11:31:13 AM7/22/19
to Opencast Users
Hi Lylian,

Unfortunately removing them is difficult.  They have to stay there unless you're willing to remove the jobs they ran, and that requires editing the core jobs database table by hand!  It's generally considered easier to just live with them, or to clear the entire jobs table at a convenient time, but then you lose your workflow history - the episodes will still show up in the admin ui, but you will not be able to see what jobs ran during processing.

G

--
To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opencast.org.

Lylian b

unread,
Jul 23, 2019, 7:04:56 AM7/23/19
to Opencast Users
Hi Greg,

Thank you for your answer. edited the database table by hand and now it's nice.


Best regards,

Lylian.

Lars Kiesow

unread,
Jul 23, 2019, 7:57:16 AM7/23/19
to us...@opencast.org
Hi,
just a slight correction for future references:

> They have to stay there unless you're willing to remove the jobs they
> ran, and that requires editing the core jobs database table by hand!

In Opencast's database, there is a connect between host registration,
service registration and jobs built with `on delete cascade` to easily
remove a host with all its services and jobs.

This means that dropping an entry from the host registration table will
remove the host just fine *but* it will also remove the services and
the jobs. This means that you loose all data about workflows run on
these nodes.

These data is still present in Elasticsearch though, meaning that just
deleting a host from the database means that you have inconsistent data
in your Opencast. To fix that, rebuild *at least* the solr workflow
index, the admin interface index and the external API index
(my recommendation: just rebuild all indexes).

In general, it's a good idea to just mess with the database if you
really know what you are doing. In this case, you could also just
disable the host using the REST interface which would have removed it
from the admin interface while keeping the data.

Best regards,
Lars

Lylian b

unread,
Jul 23, 2019, 8:22:21 AM7/23/19
to Opencast Users
Hi Lars,

Thank you for your advice, i didn't specify that we never ran any workflow with these host. I also rebuilt the solr index for security.

Best regards,

Lylian.

Ruben Gaspar

unread,
Aug 29, 2023, 3:20:12 PMAug 29
to Opencast Users, Lars Kiesow
Hi Lars,

Please could you let me know the exact API call you mentioned on this thread? I am now in a similar situation.

Thank you,
Ruben

Lars Kiesow

unread,
Sep 5, 2023, 2:35:19 PMSep 5
to Opencast Users
Hi Ruben,
the REST call I meant is:
POST /services/unregisterhost

You can easily access it from the REST docs:
https://develop.opencast.org/docs.html?path=/services#unregisterhost-12

Again: Be aware of side effects.

Best regards,
Lars
Reply all
Reply to author
Forward
0 new messages