[
https://issues.apache.org/jira/browse/KNOX-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685328#comment-16685328
]
Kevin Risden commented on KNOX-1031:
------------------------------------
[~sunilg] while looking at this noticed that there may be some information that
gets leaked or is at least incorrect from the API calls. For example, the
originalTrackingUrl and trackingUrl are both the original values not rewritten.
I don't know who/what uses this API but if trying to visit those URLs will
result in a failure. Host might also be the same issue.
[http://localhost:8443/gateway/test/yarntimeline/ws/v1/applicationhistory/]
{code:java}
<app>
<appId>application_1541786998835_0007</appId>
<currentAppAttemptId>appattempt_1541786998835_0007_000001</currentAppAttemptId>
<user>ambari-qa</user>
<name>PySparkShell</name>
<queue>default</queue>
<type>SPARK</type>
<host>172.18.0.5</host>
<rpcPort>0</rpcPort>
<appState>FINISHED</appState>
<runningContainers>0</runningContainers>
<progress>100.0</progress>
<diagnosticsInfo>Attempt recovered after RM restart</diagnosticsInfo>
<originalTrackingUrl>
ambari:18081/history/application_1541786998835_0007/1
</originalTrackingUrl>
<trackingUrl>
http://ambari:8088/proxy/application_1541786998835_0007/
</trackingUrl>
<finalAppStatus>SUCCEEDED</finalAppStatus>
<submittedTime>1541796387550</submittedTime>
<startedTime>1541796387550</startedTime>
<finishedTime>1541798018429</finishedTime>
<elapsedTime>1630879</elapsedTime>
<priority>0</priority>
<allocatedCpuVcores>0</allocatedCpuVcores>
<allocatedMemoryMB>0</allocatedMemoryMB>
<reservedCpuVcores>0</reservedCpuVcores>
<reservedMemoryMB>0</reservedMemoryMB>
<unmanagedApplication>false</unmanagedApplication>
<appNodeLabelExpression><Not set></appNodeLabelExpression>
<amNodeLabelExpression><DEFAULT_PARTITION></amNodeLabelExpression>
</app>
{code}
> Apache Hadoop Timeline Server REST API support
> ----------------------------------------------
>
> Key: KNOX-1031
> URL: https://issues.apache.org/jira/browse/KNOX-1031
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 0.13.0
> Environment: Apache Hadoop clusters, HortonWorks clusters, Cloudera
> clusters, MapR clusters
> Reporter: Pierre Beauvois
> Assignee: Sunil Govindan
> Priority: Major
> Fix For: 1.3.0
>
> Attachments: KNOX-1031.001.patch, KNOX-1031.002.patch
>
>
> Timeline Server REST API as documented here: [Timeline Server REST
> API|https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/TimelineServer.html#Timeline_Server_REST_API_v1]
> The TLS REST API provides a RESTful interface to a Timeline Server. It makes
> it easy to produce and consume messages, view the state of the cluster, and
> perform administrative actions
> This feature allow to call Timeline Server REST API through Knox. It could be
> enabled in your topology by adding the following sample:
> {code:java}
> <service>
> <role>TIMELINESERVER</role>
> <url>http://{timelineserver-host}:{timelineserver-port}</url>
> </service>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
