[jira] [Commented] (YARN-9913) In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons.
[ https://issues.apache.org/jira/browse/YARN-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16966340#comment-16966340 ] jenny commented on YARN-9913: - Added a PR. Use the RestAPI's returnValue ElapsedTime as the container‘s ElapsedTime. ( Instead of using Date.now() of the browser) > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > > > Key: YARN-9913 > URL: https://issues.apache.org/jira/browse/YARN-9913 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: image-2019-10-18-14-48-50-856.png, > image-2019-10-18-14-50-14-576.png > > > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > Please see the screenshots below: > Yarn UI2: > !image-2019-10-18-14-48-50-856.png|width=489,height=169! > Yarn UI1: > !image-2019-10-18-14-50-14-576.png|width=488,height=191! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Description: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. 1. Yarn ui1 : the ElapsedTime of running application's attempt !Yarn-AppAttempt-UI1.png|width=477,height=67! 2. Yarn ui2 : the ElapsedTime of running application's attempt a) GraphView !Yarn-AppAttempt-UI2_GraphView-1.png|width=444,height=174! !Yarn-AppAttempt-UI2_GraphView-2.png|width=440,height=168! b) GridView !Yarn-AppAttempt-UI2_GridView.png|width=451,height=165! c) GridView - container !Yarn-AppAttempt-UI2_GridView-container.png|width=439,height=106! was: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. Yarn ui1 : the ElapsedTime of running application's attempt !Yarn-AppAttempt-UI1.png|width=477,height=67! Yarn ui2 : the ElapsedTime of running application's attempt 1. GraphView !Yarn-AppAttempt-UI2_GraphView-1.png|width=444,height=174! !Yarn-AppAttempt-UI2_GraphView-2.png|width=440,height=168! 2. GridView !Yarn-AppAttempt-UI2_GridView.png|width=451,height=165! 3. GridView - container !Yarn-AppAttempt-UI2_GridView-container.png|width=439,height=106! > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png > > > In YARN ui2 attempts tab, When Browser and Yarn server are in different time > zones, the Running Application Attempt's ElapsedTime is greater than the > Application's ElapsedTime. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the browser and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. > 1. Yarn ui1 : the ElapsedTime of running application's attempt > !Yarn-AppAttempt-UI1.png|width=477,height=67! > 2. Yarn ui2 : the ElapsedTime of running application's attempt > a) GraphView > !Yarn-AppAttempt-UI2_GraphView-1.png|width=444,height=174! > !Yarn-AppAttempt-UI2_GraphView-2.png|width=440,height=168! > b) GridView > !Yarn-AppAttempt-UI2_GridView.png|width=451,height=165! > c) GridView - container > !Yarn-AppAttempt-UI2_GridView-container.png|width=439,height=106! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Attachment: (was: image-2019-10-09-17-22-31-603.png) > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png > > > In YARN ui2 attempts tab, When Browser and Yarn server are in different time > zones, the Running Application Attempt's ElapsedTime is greater than the > Application's ElapsedTime. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the browser and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. > Yarn ui1 : the ElapsedTime of running application's attempt > !Yarn-AppAttempt-UI1.png|width=477,height=67! > Yarn ui2 : the ElapsedTime of running application's attempt > 1. GraphView > !Yarn-AppAttempt-UI2_GraphView-1.png|width=444,height=174! > !Yarn-AppAttempt-UI2_GraphView-2.png|width=440,height=168! > 2. GridView > !Yarn-AppAttempt-UI2_GridView.png|width=451,height=165! > 3. GridView - container > !Yarn-AppAttempt-UI2_GridView-container.png|width=439,height=106! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Description: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. Yarn ui1 : the ElapsedTime of running application's attempt !Yarn-AppAttempt-UI1.png|width=477,height=67! Yarn ui2 : the ElapsedTime of running application's attempt 1. GraphView !Yarn-AppAttempt-UI2_GraphView-1.png|width=444,height=174! !Yarn-AppAttempt-UI2_GraphView-2.png|width=440,height=168! 2. GridView !Yarn-AppAttempt-UI2_GridView.png|width=451,height=165! 3. GridView - container !Yarn-AppAttempt-UI2_GridView-container.png|width=439,height=106! was: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. Yarn ui1 : the ElapsedTime of running application's attempt !Yarn-AppAttempt-UI1.png|width=477,height=67! Yarn ui2 : the ElapsedTime of running application's attempt 1. GraphView !Yarn-AppAttempt-UI2_GraphView-1.png|width=444,height=174! !Yarn-AppAttempt-UI2_GraphView-2.png|width=440,height=168! 2. GridView !Yarn-AppAttempt-UI2_GridView.png|width=451,height=165! 3. GridView - container > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, When Browser and Yarn server are in different time > zones, the Running Application Attempt's ElapsedTime is greater than the > Application's ElapsedTime. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the browser and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. > Yarn ui1 : the ElapsedTime of running application's attempt > !Yarn-AppAttempt-UI1.png|width=477,height=67! > Yarn ui2 : the ElapsedTime of running application's attempt > 1. GraphView > !Yarn-AppAttempt-UI2_GraphView-1.png|width=444,height=174! > !Yarn-AppAttempt-UI2_GraphView-2.png|width=440,height=168! > 2. GridView > !Yarn-AppAttempt-UI2_GridView.png|width=451,height=165! > 3. GridView - container > !Yarn-AppAttempt-UI2_GridView-container.png|width=439,height=106! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Description: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. Yarn ui1 : the ElapsedTime of running application's attempt !Yarn-AppAttempt-UI1.png|width=477,height=67! Yarn ui2 : the ElapsedTime of running application's attempt 1. GraphView !Yarn-AppAttempt-UI2_GraphView-1.png|width=444,height=174! !Yarn-AppAttempt-UI2_GraphView-2.png|width=440,height=168! 2. GridView !Yarn-AppAttempt-UI2_GridView.png|width=451,height=165! 3. GridView - container was: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. Yarn ui1 : the ElapsedTime of running application's attempt !Yarn-AppAttempt-UI1.png|width=477,height=67! Yarn ui2 : the ElapsedTime of running application's attempt 1. GraphView !Yarn-AppAttempt-UI2_GraphView-1.png|width=444,height=174! !Yarn-AppAttempt-UI2_GraphView-2.png|width=440,height=168! 2. GridView > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, When Browser and Yarn server are in different time > zones, the Running Application Attempt's ElapsedTime is greater than the > Application's ElapsedTime. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the browser and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. > Yarn ui1 : the ElapsedTime of running application's attempt > !Yarn-AppAttempt-UI1.png|width=477,height=67! > Yarn ui2 : the ElapsedTime of running application's attempt > 1. GraphView > !Yarn-AppAttempt-UI2_GraphView-1.png|width=444,height=174! > !Yarn-AppAttempt-UI2_GraphView-2.png|width=440,height=168! > 2. GridView > !Yarn-AppAttempt-UI2_GridView.png|width=451,height=165! > 3. GridView - container > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Description: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. Yarn ui1 : the ElapsedTime of running application's attempt !Yarn-AppAttempt-UI1.png|width=477,height=67! Yarn ui2 : the ElapsedTime of running application's attempt 1. GraphView !Yarn-AppAttempt-UI2_GraphView-1.png|width=444,height=174! !Yarn-AppAttempt-UI2_GraphView-2.png|width=440,height=168! 2. GridView was: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. Yarn ui1 : the ElapsedTime of running application's attempt !Yarn-AppAttempt-UI1.png|width=477,height=67! Yarn ui2 : the ElapsedTime of running application's attempt 1. GraphView !Yarn-AppAttempt-UI2_GraphView-1.png|width=544,height=213! > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, When Browser and Yarn server are in different time > zones, the Running Application Attempt's ElapsedTime is greater than the > Application's ElapsedTime. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the browser and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. > Yarn ui1 : the ElapsedTime of running application's attempt > !Yarn-AppAttempt-UI1.png|width=477,height=67! > Yarn ui2 : the ElapsedTime of running application's attempt > 1. GraphView > !Yarn-AppAttempt-UI2_GraphView-1.png|width=444,height=174! > !Yarn-AppAttempt-UI2_GraphView-2.png|width=440,height=168! > 2. GridView > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Description: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. Yarn ui1 : the ElapsedTime of running application's attempt !Yarn-AppAttempt-UI1.png|width=477,height=67! Yarn ui2 : the ElapsedTime of running application's attempt 1. GraphView !Yarn-AppAttempt-UI2_GraphView-1.png|width=544,height=213! was: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. Yarn ui1 : the ElapsedTime of running application's attempt !Yarn-AppAttempt-UI1.png|width=477,height=67! Yarn ui2 : the ElapsedTime of running application's attempt > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, When Browser and Yarn server are in different time > zones, the Running Application Attempt's ElapsedTime is greater than the > Application's ElapsedTime. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the browser and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. > Yarn ui1 : the ElapsedTime of running application's attempt > !Yarn-AppAttempt-UI1.png|width=477,height=67! > Yarn ui2 : the ElapsedTime of running application's attempt > 1. GraphView > !Yarn-AppAttempt-UI2_GraphView-1.png|width=544,height=213! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Description: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. Yarn ui1 : the ElapsedTime of running application's attempt !Yarn-AppAttempt-UI1.png|width=477,height=67! Yarn ui2 : the ElapsedTime of running application's attempt was: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, When Browser and Yarn server are in different time > zones, the Running Application Attempt's ElapsedTime is greater than the > Application's ElapsedTime. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the browser and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. > Yarn ui1 : the ElapsedTime of running application's attempt > !Yarn-AppAttempt-UI1.png|width=477,height=67! > Yarn ui2 : the ElapsedTime of running application's attempt > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Description: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. was: In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect. When Browser and Yarn server are in different time zones, the Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. I found this problem where hadoop3.1.1 was used, want to upgrade to the latest version of hadoop, but found the running Application Attempt's ElapsedTime is also incorrect. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the brower and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, When Browser and Yarn server are in different time > zones, the Running Application Attempt's ElapsedTime is greater than the > Application's ElapsedTime. > > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the browser and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Description: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. was: In YARN ui2 attempts tab, When Browser and Yarn server are in different time zones, the Running Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the browser and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, When Browser and Yarn server are in different time > zones, the Running Application Attempt's ElapsedTime is greater than the > Application's ElapsedTime. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the browser and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Description: The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, In hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, change Item memory‘s datatype from int to long. 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. 2. change Fair Scheduler API's item [memory]'s dataType from int to long. !1.png|width=524,height=103! !2.png|width=517,height=91! !3.png|width=495,height=249! was: The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, In hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, change Item memory‘s datatype from int to long. 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. 2. change Fair Scheduler API's item [memory]'s dataType from int to long. !1.png|width=524,height=103! !2.png|width=517,height=91! > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: 1.png, 2.png, 3.png, YARN-9881.001.patch > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. > > !1.png|width=524,height=103! > !2.png|width=517,height=91! > !3.png|width=495,height=249! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Description: The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, In hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, change Item memory‘s datatype from int to long. 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. 2. change Fair Scheduler API's item [memory]'s dataType from int to long. !1.png|width=524,height=103! !2.png|width=517,height=91! was: The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, In hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, change Item memory‘s datatype from int to long. 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. 2. change Fair Scheduler API's item [memory]'s dataType from int to long. !1.png|width=524,height=103! > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: 1.png, 2.png, 3.png, YARN-9881.001.patch > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. > > !1.png|width=524,height=103! > !2.png|width=517,height=91! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Description: The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, In hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, change Item memory‘s datatype from int to long. 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. 2. change Fair Scheduler API's item [memory]'s dataType from int to long. !1.png|width=524,height=103! was: The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, In hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, change Item memory‘s datatype from int to long. 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. 2. change Fair Scheduler API's item [memory]'s dataType from int to long. > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: 1.png, 2.png, 3.png, YARN-9881.001.patch > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. > > !1.png|width=524,height=103! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9913) In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons.
[ https://issues.apache.org/jira/browse/YARN-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9913: Description: In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons. Please see the screenshots below: Yarn UI2: !image-2019-10-18-14-48-50-856.png|width=489,height=169! Yarn UI1: !image-2019-10-18-14-50-14-576.png|width=488,height=191! was: In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons. Please see the screenshots below: Yarn UI2: !image-2019-10-18-14-48-50-856.png|width=567,height=196! Yarn UI1: !image-2019-10-18-14-50-14-576.png|width=573,height=224! > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > > > Key: YARN-9913 > URL: https://issues.apache.org/jira/browse/YARN-9913 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: image-2019-10-18-14-48-50-856.png, > image-2019-10-18-14-50-14-576.png > > > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > Please see the screenshots below: > Yarn UI2: > !image-2019-10-18-14-48-50-856.png|width=489,height=169! > Yarn UI1: > !image-2019-10-18-14-50-14-576.png|width=488,height=191! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9902) In NodeManagerRest, the datatype of nodeInfo's property id should be "string"
[ https://issues.apache.org/jira/browse/YARN-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9902: Description: The Yarn Rest [http://nm-http-address:port/ws/v1/node] document. In hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html#NodeManager_Information_API, change the datatype of nodeInfo's property id from long to string. !NodeManagerRest.html#NodeManager_Information_API.png|width=446,height=275! !why-change_nodeinfo-code.png|width=464,height=354! was: The Yarn Rest [http://nm-http-address:port/ws/v1/node] document. In hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html#NodeManager_Information_API, change the datatype of nodeInfo's property id from long to string. !NodeManagerRest.html#NodeManager_Information_API.png|width=446,height=275! > In NodeManagerRest, the datatype of nodeInfo's property id should be "string" > - > > Key: YARN-9902 > URL: https://issues.apache.org/jira/browse/YARN-9902 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: NodeManagerRest.html#NodeManager_Information_API.png, > YARN-9902.001.patch, why-change_nodeinfo-code.png > > > The Yarn Rest [http://nm-http-address:port/ws/v1/node] document. > In > hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html#NodeManager_Information_API, > change the datatype of nodeInfo's property id from long to string. > > !NodeManagerRest.html#NodeManager_Information_API.png|width=446,height=275! > !why-change_nodeinfo-code.png|width=464,height=354! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9902) In NodeManagerRest, the datatype of nodeInfo's property id should be "string"
[ https://issues.apache.org/jira/browse/YARN-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9902: Description: The Yarn Rest [http://nm-http-address:port/ws/v1/node] document. In hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html#NodeManager_Information_API, change the datatype of nodeInfo's property id from long to string. !NodeManagerRest.html#NodeManager_Information_API.png|width=446,height=275! was: The Yarn Rest http://nm-http-address:port/ws/v1/node document. In hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html#NodeManager_Information_API, change the datatype of nodeInfo's property id from long to string. > In NodeManagerRest, the datatype of nodeInfo's property id should be "string" > - > > Key: YARN-9902 > URL: https://issues.apache.org/jira/browse/YARN-9902 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: NodeManagerRest.html#NodeManager_Information_API.png, > YARN-9902.001.patch, why-change_nodeinfo-code.png > > > The Yarn Rest [http://nm-http-address:port/ws/v1/node] document. > In > hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html#NodeManager_Information_API, > change the datatype of nodeInfo's property id from long to string. > > !NodeManagerRest.html#NodeManager_Information_API.png|width=446,height=275! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9913) In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons.
[ https://issues.apache.org/jira/browse/YARN-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9913: Labels: pull-request-available (was: ) > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > > > Key: YARN-9913 > URL: https://issues.apache.org/jira/browse/YARN-9913 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: image-2019-10-18-14-48-50-856.png, > image-2019-10-18-14-50-14-576.png > > > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > Please see the screenshots below: > Yarn UI2: > !image-2019-10-18-14-48-50-856.png|width=567,height=196! > Yarn UI1: > !image-2019-10-18-14-50-14-576.png|width=573,height=224! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9913) In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons.
[ https://issues.apache.org/jira/browse/YARN-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954345#comment-16954345 ] jenny commented on YARN-9913: - I will fix this bug. > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > > > Key: YARN-9913 > URL: https://issues.apache.org/jira/browse/YARN-9913 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-18-14-48-50-856.png, > image-2019-10-18-14-50-14-576.png > > > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > Please see the screenshots below: > Yarn UI2: > !image-2019-10-18-14-48-50-856.png|width=567,height=196! > Yarn UI1: > !image-2019-10-18-14-50-14-576.png|width=573,height=224! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9913) In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons.
[ https://issues.apache.org/jira/browse/YARN-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9913: Description: In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons. Please see the screenshots below: Yarn UI2: !image-2019-10-18-14-48-50-856.png|width=567,height=196! Yarn UI1: !image-2019-10-18-14-50-14-576.png|width=573,height=224! was: In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons. Please see the screenshots below: Yarn UI2: !image-2019-10-18-14-48-50-856.png! > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > > > Key: YARN-9913 > URL: https://issues.apache.org/jira/browse/YARN-9913 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-18-14-48-50-856.png, > image-2019-10-18-14-50-14-576.png > > > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > Please see the screenshots below: > Yarn UI2: > !image-2019-10-18-14-48-50-856.png|width=567,height=196! > Yarn UI1: > !image-2019-10-18-14-50-14-576.png|width=573,height=224! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9913) In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons.
[ https://issues.apache.org/jira/browse/YARN-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9913: Attachment: image-2019-10-18-14-50-14-576.png > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > > > Key: YARN-9913 > URL: https://issues.apache.org/jira/browse/YARN-9913 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-18-14-48-50-856.png, > image-2019-10-18-14-50-14-576.png > > > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > Please see the screenshots below: > Yarn UI2: > !image-2019-10-18-14-48-50-856.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9913) In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons.
[ https://issues.apache.org/jira/browse/YARN-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9913: Description: In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons. Please see the screenshots below: Yarn UI2: !image-2019-10-18-14-48-50-856.png! was: In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons. Please see the screenshots below: Yarn UI2: > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > > > Key: YARN-9913 > URL: https://issues.apache.org/jira/browse/YARN-9913 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-18-14-48-50-856.png > > > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > Please see the screenshots below: > Yarn UI2: > !image-2019-10-18-14-48-50-856.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9913) In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons.
[ https://issues.apache.org/jira/browse/YARN-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9913: Attachment: image-2019-10-18-14-48-50-856.png > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > > > Key: YARN-9913 > URL: https://issues.apache.org/jira/browse/YARN-9913 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-18-14-48-50-856.png > > > In YARN ui2 attempt container tab, The Container's ElapsedTime of running > Application is incorrect when the browser and the yarn server are in > different timezons. > Please see the screenshots below: > Yarn UI2: > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-9913) In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons.
jenny created YARN-9913: --- Summary: In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons. Key: YARN-9913 URL: https://issues.apache.org/jira/browse/YARN-9913 Project: Hadoop YARN Issue Type: Bug Components: yarn-ui-v2 Affects Versions: 3.2.1, 3.1.1 Reporter: jenny In YARN ui2 attempt container tab, The Container's ElapsedTime of running Application is incorrect when the browser and the yarn server are in different timezons. Please see the screenshots below: Yarn UI2: -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9902) In NodeManagerRest, the datatype of nodeInfo's property id should be "string"
[ https://issues.apache.org/jira/browse/YARN-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951782#comment-16951782 ] jenny commented on YARN-9902: - I need review, Thanks in advance:) [~sunilg] [~wangda] [~giovanni.fumarola] > In NodeManagerRest, the datatype of nodeInfo's property id should be "string" > - > > Key: YARN-9902 > URL: https://issues.apache.org/jira/browse/YARN-9902 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: NodeManagerRest.html#NodeManager_Information_API.png, > YARN-9902.001.patch, why-change_nodeinfo-code.png > > > The Yarn Rest http://nm-http-address:port/ws/v1/node document. > In > hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html#NodeManager_Information_API, > change the datatype of nodeInfo's property id from long to string. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9902) In NodeManagerRest, the datatype of nodeInfo's property id should be "string"
[ https://issues.apache.org/jira/browse/YARN-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951705#comment-16951705 ] jenny commented on YARN-9902: - Attached patch. > In NodeManagerRest, the datatype of nodeInfo's property id should be "string" > - > > Key: YARN-9902 > URL: https://issues.apache.org/jira/browse/YARN-9902 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: NodeManagerRest.html#NodeManager_Information_API.png, > YARN-9902.001.patch, why-change_nodeinfo-code.png > > > The Yarn Rest http://nm-http-address:port/ws/v1/node document. > In > hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html#NodeManager_Information_API, > change the datatype of nodeInfo's property id from long to string. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9902) In NodeManagerRest, the datatype of nodeInfo's property id should be "string"
[ https://issues.apache.org/jira/browse/YARN-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9902: Attachment: why-change_nodeinfo-code.png NodeManagerRest.html#NodeManager_Information_API.png > In NodeManagerRest, the datatype of nodeInfo's property id should be "string" > - > > Key: YARN-9902 > URL: https://issues.apache.org/jira/browse/YARN-9902 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Reporter: jenny >Priority: Major > Attachments: NodeManagerRest.html#NodeManager_Information_API.png, > why-change_nodeinfo-code.png > > > The Yarn Rest http://nm-http-address:port/ws/v1/node document. > In > hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html#NodeManager_Information_API, > change the datatype of nodeInfo's property id from long to string. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-9902) In NodeManagerRest, the datatype of nodeInfo's property id should be "string"
jenny created YARN-9902: --- Summary: In NodeManagerRest, the datatype of nodeInfo's property id should be "string" Key: YARN-9902 URL: https://issues.apache.org/jira/browse/YARN-9902 Project: Hadoop YARN Issue Type: Bug Components: docs, documentation, yarn Reporter: jenny The Yarn Rest http://nm-http-address:port/ws/v1/node document. In hadoop-yarn/hadoop-yarn-site/NodeManagerRest.html#NodeManager_Information_API, change the datatype of nodeInfo's property id from long to string. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951474#comment-16951474 ] jenny edited comment on YARN-9881 at 10/15/19 2:10 AM: --- I need review, Thanks in advance:) [~sunilg] [~wangda] [~weiweiyagn666] [~giovanni.fumarola] was (Author: cjn082030): I need review, Thanks in advance:-) Sunil G Wangda Tan Weiwei Yang Giovanni Matteo Fumarola > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: 1.png, 2.png, 3.png, YARN-9881.001.patch > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951474#comment-16951474 ] jenny commented on YARN-9881: - I need review, Thanks in advance:-) Sunil G Wangda Tan Weiwei Yang Giovanni Matteo Fumarola > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: 1.png, 2.png, 3.png, YARN-9881.001.patch > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Attachment: (was: YARN-9881.001.patch) > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: 1.png, 2.png, 3.png > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950690#comment-16950690 ] jenny commented on YARN-9881: - Can someone review it? Thanks. > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: 1.png, 2.png, 3.png > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950691#comment-16950691 ] jenny commented on YARN-9880: - Can someone review it? Thanks. > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > I found this problem where hadoop3.1.1 was used, want to upgrade to the > latest version of hadoop, but found the running Application Attempt's > ElapsedTime is also incorrect. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the brower and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Flags: (was: Patch) Labels: pull-request-available (was: patch pull-request-available) > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: 1.png, 2.png, 3.png, YARN-9881.001.patch > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Attachment: (was: YARN-9880-001.patch) > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > I found this problem where hadoop3.1.1 was used, want to upgrade to the > latest version of hadoop, but found the running Application Attempt's > ElapsedTime is also incorrect. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the brower and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Labels: pull-request-available (was: ) > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: pull-request-available > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > I found this problem where hadoop3.1.1 was used, want to upgrade to the > latest version of hadoop, but found the running Application Attempt's > ElapsedTime is also incorrect. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the brower and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Flags: Patch Labels: patch pull-request-available (was: ) > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Labels: patch, pull-request-available > Attachments: 1.png, 2.png, 3.png, YARN-9881.001.patch > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Attachment: YARN-9881.001.patch > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: 1.png, 2.png, 3.png, YARN-9881.001.patch > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Attachment: (was: YARN-9881-001.patch) > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: 1.png, 2.png, 3.png, YARN-9881.001.patch > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Attachment: YARN-9880-001.patch > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: YARN-9880-001.patch, Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > I found this problem where hadoop3.1.1 was used, want to upgrade to the > latest version of hadoop, but found the running Application Attempt's > ElapsedTime is also incorrect. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the brower and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Attachment: Yarn-AppAttempt-UI2_GridView-container.png Yarn-AppAttempt-UI2_GridView.png Yarn-AppAttempt-UI2_GraphView-2.png Yarn-AppAttempt-UI2_GraphView-1.png Yarn-AppAttempt-UI1.png > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: Yarn-AppAttempt-UI1.png, > Yarn-AppAttempt-UI2_GraphView-1.png, Yarn-AppAttempt-UI2_GraphView-2.png, > Yarn-AppAttempt-UI2_GridView-container.png, Yarn-AppAttempt-UI2_GridView.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > I found this problem where hadoop3.1.1 was used, want to upgrade to the > latest version of hadoop, but found the running Application Attempt's > ElapsedTime is also incorrect. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the brower and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Attachment: (was: Yarn-AppAttempt-UI2.png) > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > I found this problem where hadoop3.1.1 was used, want to upgrade to the > latest version of hadoop, but found the running Application Attempt's > ElapsedTime is also incorrect. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the brower and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Attachment: (was: Yarn-AppAttempt-UI1.png) > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > I found this problem where hadoop3.1.1 was used, want to upgrade to the > latest version of hadoop, but found the running Application Attempt's > ElapsedTime is also incorrect. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the brower and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Attachment: Yarn-AppAttempt-UI2.png Yarn-AppAttempt-UI1.png > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: Yarn-AppAttempt-UI1.png, Yarn-AppAttempt-UI2.png, > image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > I found this problem where hadoop3.1.1 was used, want to upgrade to the > latest version of hadoop, but found the running Application Attempt's > ElapsedTime is also incorrect. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the brower and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Attachment: YARN-9881-001.patch > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: 1.png, 2.png, 3.png, YARN-9881-001.patch > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Attachment: 1.png 2.png 3.png Description: The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, In hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, change Item memory‘s datatype from int to long. 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. 2. change Fair Scheduler API's item [memory]'s dataType from int to long. Summary: Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. (was: In YARN ui2 attempts tab, The running Application Attempt's Container's ElapsedTime is incorrect.) > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: 1.png, 2.png, 3.png > > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) In YARN ui2 attempts tab, The running Application Attempt's Container's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Description: (was: The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, In hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, change Item memory‘s datatype from int to long. 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. 2. change Fair Scheduler API's item [memory]'s dataType from int to long.) Summary: In YARN ui2 attempts tab, The running Application Attempt's Container's ElapsedTime is incorrect. (was: Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.) > In YARN ui2 attempts tab, The running Application Attempt's Container's > ElapsedTime is incorrect. > - > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Description: The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, In hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, change Item memory‘s datatype from int to long. 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. 2. change Fair Scheduler API's item [memory]'s dataType from int to long. was: The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, In hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, change Item memory‘s datatype from int to long. 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. 2. change Fair Scheduler API's item [memory]'s dataType from int to long. !file:///C:/Users/chenjuanni/AppData/Local/YNote/data/qq00E6BD103510CE411B97708027B61D3C/c0b216d2328a491fa7a8cd592d0171cd/clipboard.png! !file:///C:/Users/chenjuanni/AppData/Local/YNote/data/qq00E6BD103510CE411B97708027B61D3C/a1e835acff194182a5cefaa31d2b3973/clipboard.png! !file:///C:/Users/chenjuanni/AppData/Local/YNote/data/qq00E6BD103510CE411B97708027B61D3C/dc19ae58affd4cecb79dba3386ddc1a9/clipboard.png! > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > --- > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) Change Cluster_Scheduler_API's Item memory‘s datatype from int to long.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Component/s: (was: yarn-ui-v2) yarn documentation docs Description: The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, In hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, change Item memory‘s datatype from int to long. 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. 2. change Fair Scheduler API's item [memory]'s dataType from int to long. !file:///C:/Users/chenjuanni/AppData/Local/YNote/data/qq00E6BD103510CE411B97708027B61D3C/c0b216d2328a491fa7a8cd592d0171cd/clipboard.png! !file:///C:/Users/chenjuanni/AppData/Local/YNote/data/qq00E6BD103510CE411B97708027B61D3C/a1e835acff194182a5cefaa31d2b3973/clipboard.png! !file:///C:/Users/chenjuanni/AppData/Local/YNote/data/qq00E6BD103510CE411B97708027B61D3C/dc19ae58affd4cecb79dba3386ddc1a9/clipboard.png! Summary: Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. (was: In YARN ui2 attempts tab, The running Application Attempt's Container's ElapsedTime is incorrect.) > Change Cluster_Scheduler_API's Item memory‘s datatype from int to long. > --- > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: docs, documentation, yarn >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > > The Yarn Rest [http://rm-http-address:port/ws/v1/cluster/scheduler] document, > In > hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html#Cluster_Scheduler_API, > change Item memory‘s datatype from int to long. > 1.change Capacity Scheduler API's item [memory]'s dataType from int to long. > 2. change Fair Scheduler API's item [memory]'s dataType from int to long. > !file:///C:/Users/chenjuanni/AppData/Local/YNote/data/qq00E6BD103510CE411B97708027B61D3C/c0b216d2328a491fa7a8cd592d0171cd/clipboard.png! > > !file:///C:/Users/chenjuanni/AppData/Local/YNote/data/qq00E6BD103510CE411B97708027B61D3C/a1e835acff194182a5cefaa31d2b3973/clipboard.png! > > !file:///C:/Users/chenjuanni/AppData/Local/YNote/data/qq00E6BD103510CE411B97708027B61D3C/dc19ae58affd4cecb79dba3386ddc1a9/clipboard.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9881) In YARN ui2 attempts tab, The running Application Attempt's Container's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949305#comment-16949305 ] jenny commented on YARN-9881: - Hi [~Prabhu Joseph] , I will attach details, please don't close, thank you > In YARN ui2 attempts tab, The running Application Attempt's Container's > ElapsedTime is incorrect. > - > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Description: In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect. When Browser and Yarn server are in different time zones, the Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. I found this problem where hadoop3.1.1 was used, want to upgrade to the latest version of hadoop, but found the running Application Attempt's ElapsedTime is also incorrect. In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from brower. Therefore, when the brower and the yarn server are in different time zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. was: In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect. When Browser and Yarn server are in different time zones, the Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > I found this problem where hadoop3.1.1 was used, want to upgrade to the > latest version of hadoop, but found the running Application Attempt's > ElapsedTime is also incorrect. > In UI1, get ElapsedTime from yarn server. In UI2, get currentTime from > brower. Therefore, when the brower and the yarn server are in different time > zones, the ElapsedTime is incorrect. While the Application‘s ElapsedTime is > 29 Secs, the Application Attempt's ElapsedTime is 10 Hrs : 49 Mins : 55 Secs. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16947476#comment-16947476 ] jenny edited comment on YARN-9880 at 10/9/19 9:27 AM: -- Hi [~Prabhu Joseph] , please see the screenshots (UI2) . UI1 is right. was (Author: cjn082030): Hi [~Prabhu Joseph] , please see the screenshots . > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16947476#comment-16947476 ] jenny commented on YARN-9880: - Hi [~Prabhu Joseph] , please see the screenshots . > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Attachment: image-2019-10-09-17-23-08-311.png > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Attachment: (was: image-2019-10-09-17-23-08-311.png) > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Attachment: image-2019-10-09-17-22-31-603.png > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > Attachments: image-2019-10-09-17-22-31-603.png > > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9880: Description: In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect. When Browser and Yarn server are in different time zones, the Application Attempt's ElapsedTime is greater than the Application's ElapsedTime. > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > - > > Key: YARN-9880 > URL: https://issues.apache.org/jira/browse/YARN-9880 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > > In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is > incorrect. > When Browser and Yarn server are in different time zones, the Application > Attempt's ElapsedTime is greater than the Application's ElapsedTime. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-9881) In YARN ui2 attempts tab, The running Application Attempt's Container's ElapsedTime is incorrect.
[ https://issues.apache.org/jira/browse/YARN-9881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jenny updated YARN-9881: Summary: In YARN ui2 attempts tab, The running Application Attempt's Container's ElapsedTime is incorrect. (was: In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.) > In YARN ui2 attempts tab, The running Application Attempt's Container's > ElapsedTime is incorrect. > - > > Key: YARN-9881 > URL: https://issues.apache.org/jira/browse/YARN-9881 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Affects Versions: 3.1.1, 3.2.1 >Reporter: jenny >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-9881) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
jenny created YARN-9881: --- Summary: In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect. Key: YARN-9881 URL: https://issues.apache.org/jira/browse/YARN-9881 Project: Hadoop YARN Issue Type: Bug Components: yarn-ui-v2 Affects Versions: 3.2.1, 3.1.1 Reporter: jenny -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-9880) In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect.
jenny created YARN-9880: --- Summary: In YARN ui2 attempts tab, The running Application Attempt's ElapsedTime is incorrect. Key: YARN-9880 URL: https://issues.apache.org/jira/browse/YARN-9880 Project: Hadoop YARN Issue Type: Bug Components: yarn-ui-v2 Affects Versions: 3.2.1, 3.1.1 Reporter: jenny -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-9878) the
jenny created YARN-9878: --- Summary: the Key: YARN-9878 URL: https://issues.apache.org/jira/browse/YARN-9878 Project: Hadoop YARN Issue Type: Bug Components: yarn-ui-v2 Affects Versions: 3.2.1, 3.1.1 Reporter: jenny -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-9381) The yarn-default.xml has two identical property named yarn.timeline-service.http-cross-origin.enabled
jenny created YARN-9381: --- Summary: The yarn-default.xml has two identical property named yarn.timeline-service.http-cross-origin.enabled Key: YARN-9381 URL: https://issues.apache.org/jira/browse/YARN-9381 Project: Hadoop YARN Issue Type: Improvement Components: yarn Affects Versions: 3.1.2, 3.1.1, 3.2.0, 3.1.0 Reporter: jenny Attachments: image-2019-03-12-16-51-19-748.png The yarn-default.xml file has two identical property named yarn.timeline-service.http-cross-origin.enabled. !image-2019-03-12-16-51-19-748.png|width=298,height=98! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
