Right, this is 1.1.0 and 2.7.0.0. The only thing I can think of is it's coming from the job-tracker field in the job submission. We use an internal cluster reference here as the job, oozie and submission mechanism are all on the cluster. While we could use a 'Knoxified" reference here, is this what people are generally doing? I guess it's fine if it's only used to display a link the UI, but I'd worry a little if programmatic API access between the job and YARN was being routed this way?
Cheers, /ailuropod4 On Wed, Aug 8, 2018 at 8:37 PM, Sandeep Moré <moresand...@gmail.com> wrote: > This should not be the case, this should work, especially with Ambari 2.7, > I am assuming this is Knox 1.1.0 right ? > > Best, > Sandeep > > On Wed, Aug 8, 2018 at 8:39 PM T Smith <ailurop...@gmail.com> wrote: > >> Hi all, >> >> It seems like the Oozie workflow manager view Job URL link points to an >> internal cluster node rather than the external knox location for YARN, e.g. >> http://somecluster-hadoop-mgr-1.node.local:8088/proxy/ >> application_1533747863444_0017/ instead of https://knox:8443/gateway/ >> something/yarn/proxy/application_1533747863444_0017/ >> >> This means that this view has limited usability through Knox as things >> stand. >> >> Do we know i this a Knox issue, an Ambari issue, or a user issue (i.e. >> was I supposed to configure something!) ? >> >> Cheers, >> /ailuropod4 >> >>
