You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2016/08/25 16:58:21 UTC
[jira] [Comment Edited] (TEZ-3418) Tez UI/UI2 doesn't support
kerberized cluster
[ https://issues.apache.org/jira/browse/TEZ-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437211#comment-15437211 ]
Hitesh Shah edited comment on TEZ-3418 at 8/25/16 4:57 PM:
-----------------------------------------------------------
Hello [~BigDataOrange], could you provide a few more details on what you are looking at?
I believe this is something which probably needs a lot more documentation in terms of potential approaches. One such approach that can be leveraged is by hosting the ui war within the YARN timeline server. Another approach that would need code changes is setting up a jetty server to host the UI with the various hadoop auth filters in place to simplify the setup in a kerberized env.
If you have tried any approaches, would you mind sharing your findings on what issues you hit?
was (Author: hitesh):
Hello [~BigDataOrange], could you provide a few more details on what you are looking at?
I believe this is something which probably needs a lot more documentation in terms of potential approaches. One such approach that can be leveraged is by hosting the UI within the YARN timeline server.
If you have tried any approaches, would you mind sharing your findings on what issues you hit?
> Tez UI/UI2 doesn't support kerberized cluster
> ---------------------------------------------
>
> Key: TEZ-3418
> URL: https://issues.apache.org/jira/browse/TEZ-3418
> Project: Apache Tez
> Issue Type: Improvement
> Components: UI
> Affects Versions: 0.8.3
> Environment: Tez 0.8.3, Hadoop 2.7.2
> Reporter: Alexandre Linte
>
> Today it is not possible to use Tez UI/UI2 in a Kerberized cluster without Ambari.
> This feature request asks for an improvement of the Tez UI2 in order to fully support Kerberos.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)