Opencast 9 and Elasticsearch

128 views
Skip to first unread message

s.la...@googlemail.com

unread,
Jun 4, 2021, 2:51:25 AM6/4/21
to Opencast Users
Hello,

at the moment I'm playing around with Opencast 9 and am planning on upgrading to Opencast 9/10 at the end of summer.
Does the new elastic search service need to be running on one of the Opencast servers or can it be run on its own machine and how do I achieve this? Which version of elastic search ist needed and how should it be configured?

Unfortunately there is not much documentation on this topic (https://docs.opencast.org/r/9.x/admin/#configuration/elasticsearch/) or didn't I find it?

Best regards
Sven

itz.feli...@gmail.com

unread,
Jun 4, 2021, 3:07:49 AM6/4/21
to Opencast Users, s.la...@googlemail.com
Hi Sven,

there is more documentation on the installation guides https://docs.opencast.org/r/9.x/admin/#installation/debs/ (section "Install Elasticsearch") or https://docs.opencast.org/r/9.x/admin/#installation/source-linux/ "Install Dependencies"

We are already upgraded one of our Opencast installations (for HS Anhalt). When in doubt, I usually have a look at the docker compose files provided by Matthias https://github.com/opencast/opencast-docker/blob/master/docker-compose/docker-compose.multiserver.mariadb.yml#L46

> Does the new elastic search service need to be running on one of the Opencast servers or can it be run on its own machine and how do I achieve this?

It can run elsewhere. What I can't tell you, yet, is which opencast nodes (admin/ ingest/ presentation) have to be allowed to connect to it.

> Which version of elastic search ist needed and how should it be configured?

We use the suggested elasticsearch:7.9.3 (docker image) and almost no configuration was required. The only thing, I took care of was the data volume and the handy environment variable TAKE_FILE_OWNERSHIP which chown's all data files and the data dir when ES is started.

For reference, here is our docker-compose file entry:

elasticsearch:
  image: elasticsearch:7.9.3
  restart: always
  environment:
    TAKE_FILE_OWNERSHIP: 1
    discovery.type: single-node
  ports:
    - "9200:9200"
  volumes:
    - ./volumes/elasticsearch/:/usr/share/elasticsearch/data

Don't forget to add proper firewall rules for Port 9200, then.

Kind regards,
Felix

Greg Logan

unread,
Jun 4, 2021, 11:07:56 AM6/4/21
to Opencast Users
Hi Felix,

With opencast 10 only the admin node requires access to ES thanks to the work from Elan. Prior to that all nodes require it if I remember right. 

G

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

s.la...@googlemail.com

unread,
Jun 7, 2021, 4:07:31 AM6/7/21
to Opencast Users, itz.feli...@gmail.com, s.la...@googlemail.com
Hi Felix,

thanks for your hint where to look. I think I searched only in the configuration section.

Regards
Sven

Lars Kiesow

unread,
Jun 7, 2021, 6:40:10 AM6/7/21
to us...@opencast.org
That is not correct. Only admin needs access regardless of the Opencast
version. That's why we usually recommend running it on the admin node
and having it listen to localhost only. But you can, of course, run it
as a dedicated host.

Greg was confusing Elasticsearch with ActiveMQ.

–Lars
Reply all
Reply to author
Forward
0 new messages