We have now finished the migration from Oozie to Airflow, so as far as I know oozie is no longer required.
https://wikitech.wikimedia.org/wiki/Data_Engineering/Systems/Cluster/Oozie
https://wikitech.wikimedia.org/wiki/Data_Engineering/Systems/Cluster/Oozie/Administration
However, the oozie services are still running on an-coord1001 and an-test-coord1001 and we still have alerts configured in Icinga
btullis@an-coord1001:~$ oozie admin -servers Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/usr/lib/oozie/lib/log4j-slf4j-impl-2.17.0.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/usr/lib/oozie/lib/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/usr/lib/oozie/lib/slf4j-simple-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory] an-coord1001.eqiad.wmnet : http://an-coord1001.eqiad.wmnet:11000/oozie
There is also a known vulnerability that affects our version of oozie (T212416) so I propose that we stop the service and remove both server and client components.
Tagging Data-Engineering as they will be able to say with more certainty whether or not it is truly deprecated.