[ 
https://issues.apache.org/jira/browse/YARN-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273408#comment-15273408
 ] 

Wangda Tan commented on YARN-5000:
----------------------------------

[~sunilg],

Tested the patch, haven't done deep tests, some comments so far

1) When I try the patch, run RM without TS/NM. The application is in ACCEPTED 
state, but the application page has multiple entries of attempt: (see 
[attachment|https://issues.apache.org/jira/secure/attachment/12802571/screenshot-1.png]),
 (This only happens when I access RM hosted page at localhost:8288, probably 
caused by auto/hash issue which is mentioned by you at: 
https://issues.apache.org/jira/browse/YARN-4515?focusedCommentId=15269292&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15269292).

2) When an application is running (without enable TS, but NM is running). I get 
following intermittent exception when keep refreshing page at: 
{{http://localhost:4200/yarnAppAttempt/appattempt_1462494543748_0004_000001 
(replace by your attempt ID}}
{code}
http://localhost:1337/localhost:8088/ws/v1/cluster/apps/application_1462494543748_0004/appattempts/appattempt_1462494543748_0004_000001/containers
yarn-container.js:31 
http://localhost:1337/localhost:8188/ws/v1/applicationhistory/apps/applicat…494543748_0004/appattempts/appattempt_1462494543748_0004_000001/containers
ember.debug.js:30877 TypeError: Cannot read property '0' of undefined
    at Class.error (application.js:11)
    at Object.triggerEvent (ember.debug.js:27476)
    at Object.trigger (ember.debug.js:51925)
    at Object.trigger (ember.debug.js:51739)
    at ember.debug.js:51559
    at tryCatch (ember.debug.js:52258)
    at invokeCallback (ember.debug.js:52273)
    at publish (ember.debug.js:52241)
    at publishRejection (ember.debug.js:52176)
    at ember.debug.js:30835onerrorDefault @ ember.debug.js:30877trigger @ 
ember.debug.js:52928(anonymous function) @ ember.debug.js:54177invoke @ 
ember.debug.js:320flush @ ember.debug.js:384flush @ ember.debug.js:185end @ 
ember.debug.js:563run @ ember.debug.js:685run @ 
ember.debug.js:20105hash.success @ rest-adapter.js:742fire @ 
jquery.js:3099fireWith @ jquery.js:3211done @ jquery.js:8264(anonymous 
function) @ jquery.js:8605
jquery.js:8630 GET 
http://localhost:1337/localhost:8188/ws/v1/applicationhistory/apps/applicat…494543748_0004/appattempts/appattempt_1462494543748_0004_000001/containers
 502 (Bad Gateway)
{code}

3) (MINOR), I can get this error at console when TS is not enabled:
{{jquery.js:8630 GET 
http://localhost:1337/localhost:8188/ws/v1/applicationhistory/apps/applicat…494543748_0004/appattempts/appattempt_1462494543748_0004_000001/containers
 502 (Bad Gateway)}}, probably we should not show such message

For code implementation, some comments so far:
1) Instead of returning object with id="dummy" and check "dummy" everywhere, is 
it possible to return an empty array? Which may be more clear.

> [YARN-3368] App attempt page is not loading when timeline server is not 
> started
> -------------------------------------------------------------------------------
>
>                 Key: YARN-5000
>                 URL: https://issues.apache.org/jira/browse/YARN-5000
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: 0001-YARN-5000.patch, 
> AppFinishedAndNoTimelineServer.png, AppRunningAndNoTimelineServer.png, 
> AppRunningAndNoTimelineServer_v2.png, YARN-5000-YARN-3368.1.patch, 
> YARN-5000-YARN-3368.2.patch, YARN-5000-YARN-3368.3.patch, 
> YARN-5000-YARN-3368.4.patch, screenshot-1.png
>
>
> If timeline server is not started, app attempt page is not getting loaded.
> In new web-ui, yarnContainer route is tightly coupled with both RM and 
> Timeline server. And if one of server is not up, page will not load. If 
> timeline server is not up, container information from RM is to be displayed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to