Hello Andras,
I can reproduce it by just typing the http://:11000 on the
browser. This is an AWS EMR 5.0.3 with Oozie version 4.2.0.
We created 3 EMR clusters recently of this version, and all three have this
problem. I'm about to take this to AWS but wanted to check here if anyone
has
Hi Suresh,
can you please provide following details:
- what are the exact and minimal steps to reproduce, aka what does that
exactly mean "when accessing the Oozie web client"?
- what is the Oozie version you're trying? Or did you build that from
master?
- when trying w/ Tomcat
