[jira] [Commented] (YARN-8115) [UI2] URL data like nodeHTTPAddress must be encoded in UI before using for NM/ATS
[ https://issues.apache.org/jira/browse/YARN-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425637#comment-16425637 ] Sreenath Somarajapuram commented on YARN-8115: -- [~sunilg] Please review the patch. > [UI2] URL data like nodeHTTPAddress must be encoded in UI before using for > NM/ATS > - > > Key: YARN-8115 > URL: https://issues.apache.org/jira/browse/YARN-8115 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sunil G >Assignee: Sreenath Somarajapuram >Priority: Major > Attachments: YARN-8115.001.patch > > > nodeHTTPAddress is picked from RM ,but it should be encoded before processing > it from UI -- 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
[jira] [Updated] (YARN-8115) [UI2] URL data like nodeHTTPAddress must be encoded in UI before using for NM/ATS
[ https://issues.apache.org/jira/browse/YARN-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-8115: - Attachment: YARN-8115.001.patch > [UI2] URL data like nodeHTTPAddress must be encoded in UI before using for > NM/ATS > - > > Key: YARN-8115 > URL: https://issues.apache.org/jira/browse/YARN-8115 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Sunil G >Assignee: Sreenath Somarajapuram >Priority: Major > Attachments: YARN-8115.001.patch > > > nodeHTTPAddress is picked from RM ,but it should be encoded before processing > it from UI -- 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
[jira] [Commented] (YARN-8066) RM/UI2: doughnut chart mis-rendering
[ https://issues.apache.org/jira/browse/YARN-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412534#comment-16412534 ] Sreenath Somarajapuram commented on YARN-8066: -- [~sunilg] Attached a patch. Please help in merging the same. > RM/UI2: doughnut chart mis-rendering > > > Key: YARN-8066 > URL: https://issues.apache.org/jira/browse/YARN-8066 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Zoltan Haindrich >Assignee: Sreenath Somarajapuram >Priority: Major > Attachments: YARN-8066.1.patch, donut.png, more_applications.png, > screenshot.png > > > on the overview page; > http://ctr-e138-1518143905142-140659-01-02.hwx.site:8088/ui2/#/cluster-overview > * when there are 2 subqueues to the root (llap and default); > * the llap queue is running 1 application > * there are no other active application > the doughtut chart is rendered incorrectly...like something have eaten some > part of it > the same thing can be observed when there are other applications are active > while watching the animation during refresh - in that case the incorrect > drawing appears a number of time during animation - but at the end it > stabilizes as a correct.. -- 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
[jira] [Updated] (YARN-8066) RM/UI2: doughnut chart mis-rendering
[ https://issues.apache.org/jira/browse/YARN-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-8066: - Attachment: YARN-8066.1.patch > RM/UI2: doughnut chart mis-rendering > > > Key: YARN-8066 > URL: https://issues.apache.org/jira/browse/YARN-8066 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Zoltan Haindrich >Assignee: Sreenath Somarajapuram >Priority: Major > Attachments: YARN-8066.1.patch, donut.png, more_applications.png, > screenshot.png > > > on the overview page; > http://ctr-e138-1518143905142-140659-01-02.hwx.site:8088/ui2/#/cluster-overview > * when there are 2 subqueues to the root (llap and default); > * the llap queue is running 1 application > * there are no other active application > the doughtut chart is rendered incorrectly...like something have eaten some > part of it > the same thing can be observed when there are other applications are active > while watching the animation during refresh - in that case the incorrect > drawing appears a number of time during animation - but at the end it > stabilizes as a correct.. -- 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
[jira] [Commented] (YARN-8066) RM/UI2: doughnut chart mis-rendering
[ https://issues.apache.org/jira/browse/YARN-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412532#comment-16412532 ] Sreenath Somarajapuram commented on YARN-8066: -- The issue was reproducible on Chrome/Chromium browsers in the Debian OS. It was because arcs with value 0 were getting rendered as one big white circle! Will attach a patch shortly that fixes the same by controlling the visibility of such arcs. > RM/UI2: doughnut chart mis-rendering > > > Key: YARN-8066 > URL: https://issues.apache.org/jira/browse/YARN-8066 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Zoltan Haindrich >Assignee: Sreenath Somarajapuram >Priority: Major > Attachments: donut.png, more_applications.png, screenshot.png > > > on the overview page; > http://ctr-e138-1518143905142-140659-01-02.hwx.site:8088/ui2/#/cluster-overview > * when there are 2 subqueues to the root (llap and default); > * the llap queue is running 1 application > * there are no other active application > the doughtut chart is rendered incorrectly...like something have eaten some > part of it > the same thing can be observed when there are other applications are active > while watching the animation during refresh - in that case the incorrect > drawing appears a number of time during animation - but at the end it > stabilizes as a correct.. -- 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
[jira] [Assigned] (YARN-8066) RM/UI2: doughnut chart mis-rendering
[ https://issues.apache.org/jira/browse/YARN-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram reassigned YARN-8066: Assignee: Sreenath Somarajapuram > RM/UI2: doughnut chart mis-rendering > > > Key: YARN-8066 > URL: https://issues.apache.org/jira/browse/YARN-8066 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Zoltan Haindrich >Assignee: Sreenath Somarajapuram >Priority: Major > Attachments: donut.png, more_applications.png, screenshot.png > > > on the overview page; > http://ctr-e138-1518143905142-140659-01-02.hwx.site:8088/ui2/#/cluster-overview > * when there are 2 subqueues to the root (llap and default); > * the llap queue is running 1 application > * there are no other active application > the doughtut chart is rendered incorrectly...like something have eaten some > part of it > the same thing can be observed when there are other applications are active > while watching the animation during refresh - in that case the incorrect > drawing appears a number of time during animation - but at the end it > stabilizes as a correct.. -- 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
[jira] [Updated] (YARN-8066) RM/UI2: doughnut chart mis-rendering
[ https://issues.apache.org/jira/browse/YARN-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-8066: - Attachment: donut.png > RM/UI2: doughnut chart mis-rendering > > > Key: YARN-8066 > URL: https://issues.apache.org/jira/browse/YARN-8066 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Zoltan Haindrich >Priority: Major > Attachments: donut.png, more_applications.png, screenshot.png > > > on the overview page; > http://ctr-e138-1518143905142-140659-01-02.hwx.site:8088/ui2/#/cluster-overview > * when there are 2 subqueues to the root (llap and default); > * the llap queue is running 1 application > * there are no other active application > the doughtut chart is rendered incorrectly...like something have eaten some > part of it > the same thing can be observed when there are other applications are active > while watching the animation during refresh - in that case the incorrect > drawing appears a number of time during animation - but at the end it > stabilizes as a correct.. -- 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
[jira] [Updated] (YARN-7802) Application regex search did not work properly with app name
[ https://issues.apache.org/jira/browse/YARN-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-7802: - Attachment: YARN-7802.2.patch > Application regex search did not work properly with app name > > > Key: YARN-7802 > URL: https://issues.apache.org/jira/browse/YARN-7802 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Yesha Vora >Assignee: Sreenath Somarajapuram >Priority: Major > Attachments: YARN-7802.1.patch, YARN-7802.2.patch > > > Steps: > 1) Start yarn services with "yesha-hbase-retry-2" > 2) put regex = yesha-hbase-retry-2 > http://host:8088/ui2/#/yarn-apps/apps?searchText=yesha-hbase-retry-2 > Here, the application does not gets listed. The regex work with > "yesha-hbase-retry-" input but does not work with full app name. -- 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
[jira] [Commented] (YARN-7802) Application regex search did not work properly with app name
[ https://issues.apache.org/jira/browse/YARN-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346490#comment-16346490 ] Sreenath Somarajapuram commented on YARN-7802: -- [~sunil.gov...@gmail.com] Please review the patch. > Application regex search did not work properly with app name > > > Key: YARN-7802 > URL: https://issues.apache.org/jira/browse/YARN-7802 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Yesha Vora >Assignee: Sreenath Somarajapuram >Priority: Major > Attachments: YARN-7802.1.patch > > > Steps: > 1) Start yarn services with "yesha-hbase-retry-2" > 2) put regex = yesha-hbase-retry-2 > http://host:8088/ui2/#/yarn-apps/apps?searchText=yesha-hbase-retry-2 > Here, the application does not gets listed. The regex work with > "yesha-hbase-retry-" input but does not work with full app name. -- 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
[jira] [Updated] (YARN-7802) Application regex search did not work properly with app name
[ https://issues.apache.org/jira/browse/YARN-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-7802: - Attachment: YARN-7802.1.patch > Application regex search did not work properly with app name > > > Key: YARN-7802 > URL: https://issues.apache.org/jira/browse/YARN-7802 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Yesha Vora >Priority: Major > Attachments: YARN-7802.1.patch > > > Steps: > 1) Start yarn services with "yesha-hbase-retry-2" > 2) put regex = yesha-hbase-retry-2 > http://host:8088/ui2/#/yarn-apps/apps?searchText=yesha-hbase-retry-2 > Here, the application does not gets listed. The regex work with > "yesha-hbase-retry-" input but does not work with full app name. -- 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
[jira] [Assigned] (YARN-7802) Application regex search did not work properly with app name
[ https://issues.apache.org/jira/browse/YARN-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram reassigned YARN-7802: Assignee: Sreenath Somarajapuram > Application regex search did not work properly with app name > > > Key: YARN-7802 > URL: https://issues.apache.org/jira/browse/YARN-7802 > Project: Hadoop YARN > Issue Type: Bug > Components: yarn-ui-v2 >Reporter: Yesha Vora >Assignee: Sreenath Somarajapuram >Priority: Major > Attachments: YARN-7802.1.patch > > > Steps: > 1) Start yarn services with "yesha-hbase-retry-2" > 2) put regex = yesha-hbase-retry-2 > http://host:8088/ui2/#/yarn-apps/apps?searchText=yesha-hbase-retry-2 > Here, the application does not gets listed. The regex work with > "yesha-hbase-retry-" input but does not work with full app name. -- 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
[jira] [Updated] (YARN-7436) YARN UI: Upgrade to the latest em-table
[ https://issues.apache.org/jira/browse/YARN-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-7436: - Attachment: YARN-7436.1.patch [~sunilg] [~skmvasu] Please help in reviewing the patch. > YARN UI: Upgrade to the latest em-table > --- > > Key: YARN-7436 > URL: https://issues.apache.org/jira/browse/YARN-7436 > Project: Hadoop YARN > Issue Type: Bug > Components: webapp >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Major > Attachments: YARN-7436.1.patch > > > Similar to TEZ-3842, upgrade the em-table version to take advantage of the > new features. > - em-table have improved a lot in the past few months. SQL like advanced > searching capability and Faceted filters are the best among them. > \cc [~skmvasu] [~sunilg] -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7436) YARN UI: Upgrade to the latest em-table
[ https://issues.apache.org/jira/browse/YARN-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-7436: - Description: Similar to TEZ-3842, upgrade the em-table version to take advantage of the new features. - em-table have improved a lot in the past few months. SQL like advanced searching capability and Faceted filters are the best among them. \cc [~skmvasu] [~sunilg] was: Similar to TEZ-3842, upgrade the em-table version to take advantage of the new features. - em-table have improved a lot in the past few months. SQL like advanced searching capability and Faceted filters are the best among them. > YARN UI: Upgrade to the latest em-table > --- > > Key: YARN-7436 > URL: https://issues.apache.org/jira/browse/YARN-7436 > Project: Hadoop YARN > Issue Type: Bug > Components: webapp >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram >Priority: Major > > Similar to TEZ-3842, upgrade the em-table version to take advantage of the > new features. > - em-table have improved a lot in the past few months. SQL like advanced > searching capability and Faceted filters are the best among them. > \cc [~skmvasu] [~sunilg] -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-7436) YARN UI: Upgrade to the latest em-table
Sreenath Somarajapuram created YARN-7436: Summary: YARN UI: Upgrade to the latest em-table Key: YARN-7436 URL: https://issues.apache.org/jira/browse/YARN-7436 Project: Hadoop YARN Issue Type: Bug Components: webapp Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram Priority: Major Similar to TEZ-3842, upgrade the em-table version to take advantage of the new features. - em-table have improved a lot in the past few months. SQL like advanced searching capability and Faceted filters are the best among them. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7170) Investigate bower dependencies for YARN UI v2
[ https://issues.apache.org/jira/browse/YARN-7170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203531#comment-16203531 ] Sreenath Somarajapuram commented on YARN-7170: -- +1 As pointed out by [~sunilg], v2 patch helps in mitigating the impediment issues. Once bower-shrinkwrap-resolver-ext is removed, the semver based dependency resolution would start picking the latest available version that matches the pattern. In IDEAL SITUATIONS that shouldn't cause any issues, and considering that we are moving towards a better method for bower side dependency resolution, things must be fine down the line. > Investigate bower dependencies for YARN UI v2 > - > > Key: YARN-7170 > URL: https://issues.apache.org/jira/browse/YARN-7170 > Project: Hadoop YARN > Issue Type: Bug > Components: webapp >Reporter: Sunil G >Assignee: Sunil G >Priority: Critical > Attachments: YARN-7170.001.patch, YARN-7170.002.patch > > > [INFO] bower ember#2.2.0 progress Receiving > objects: 50% (38449/75444), 722.46 MiB | 3.30 MiB/s > ... > [INFO] bower ember#2.2.0 progress Receiving > objects: 99% (75017/75444), 1.56 GiB | 3.31 MiB/s > Investigate the dependencies and reduce the download size and speed of > compilation. > cc/ [~Sreenath] and [~akhilpb] -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6458) New Yarn UI: Lock down dependency versions
[ https://issues.apache.org/jira/browse/YARN-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-6458: - Attachment: YARN-6458.3.patch [~sunilg] Attaching a rebased patch. > New Yarn UI: Lock down dependency versions > -- > > Key: YARN-6458 > URL: https://issues.apache.org/jira/browse/YARN-6458 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-6458.1.patch, YARN-6458.2.patch, YARN-6458.3.patch > > > As we use semver to denote dependency version, every time a new build is > made, the latest available version of the dependency would be downloaded. > This affects the reliability of the UI build. Hence we must lockdown the > dependencies. > Lockdown must happen in both the package managers used by the UI - NPM & > Bower. > Yarn: > Replace NPM with Yarn. Yarn is a package manager developed to solve this > issue and many more. It also enables offline build. > Bower: > Bower shrinkwrap resolver plugin can be used to lock the dependency versions. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6458) New Yarn UI: Lock down dependency versions
[ https://issues.apache.org/jira/browse/YARN-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-6458: - Attachment: YARN-6458.2.patch [~sunilg] Attaching a fresh patch with ember-truth-helpers version upgraded. > New Yarn UI: Lock down dependency versions > -- > > Key: YARN-6458 > URL: https://issues.apache.org/jira/browse/YARN-6458 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-6458.1.patch, YARN-6458.2.patch > > > As we use semver to denote dependency version, every time a new build is > made, the latest available version of the dependency would be downloaded. > This affects the reliability of the UI build. Hence we must lockdown the > dependencies. > Lockdown must happen in both the package managers used by the UI - NPM & > Bower. > Yarn: > Replace NPM with Yarn. Yarn is a package manager developed to solve this > issue and many more. It also enables offline build. > Bower: > Bower shrinkwrap resolver plugin can be used to lock the dependency versions. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6458) New Yarn UI: Lock down dependency versions
[ https://issues.apache.org/jira/browse/YARN-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-6458: - Attachment: YARN-6458.1.patch Please help in reviewing the patch. > New Yarn UI: Lock down dependency versions > -- > > Key: YARN-6458 > URL: https://issues.apache.org/jira/browse/YARN-6458 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-6458.1.patch > > > As we use semver to denote dependency version, every time a new build is > made, the latest available version of the dependency would be downloaded. > This affects the reliability of the UI build. Hence we must lockdown the > dependencies. > Lockdown must happen in both the package managers used by the UI - NPM & > Bower. > Yarn: > Replace NPM with Yarn. Yarn is a package manager developed to solve this > issue and many more. It also enables offline build. > Bower: > Bower shrinkwrap resolver plugin can be used to lock the dependency versions. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6458) Yarn UI: Lock down dependency versions
[ https://issues.apache.org/jira/browse/YARN-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962563#comment-15962563 ] Sreenath Somarajapuram commented on YARN-6458: -- TEZ-3285 is the counterpart of this ticket in Tez project. > Yarn UI: Lock down dependency versions > -- > > Key: YARN-6458 > URL: https://issues.apache.org/jira/browse/YARN-6458 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > > As we use semver to denote dependency version, every time a new build is > made, the latest available version of the dependency would be downloaded. > This affects the reliability of the UI build. Hence we must lockdown the > dependencies. > Lockdown must happen in both the package managers used by the UI - NPM & > Bower. > Yarn: > Replace NPM with Yarn. Yarn is a package manager developed to solve this > issue and many more. It also enables offline build. > Bower: > Bower shrinkwrap resolver plugin can be used to lock the dependency versions. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6458) Yarn UI: Lock down dependency versions
Sreenath Somarajapuram created YARN-6458: Summary: Yarn UI: Lock down dependency versions Key: YARN-6458 URL: https://issues.apache.org/jira/browse/YARN-6458 Project: Hadoop YARN Issue Type: Bug Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram As we use semver to denote dependency version, every time a new build is made, the latest available version of the dependency would be downloaded. This affects the reliability of the UI build. Hence we must lockdown the dependencies. Lockdown must happen in both the package managers used by the UI - NPM & Bower. Yarn: Replace NPM with Yarn. Yarn is a package manager developed to solve this issue and many more. It also enables offline build. Bower: Bower shrinkwrap resolver plugin can be used to lock the dependency versions. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6278) -Pyarn-ui build seems broken in trunk
[
https://issues.apache.org/jira/browse/YARN-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894826#comment-15894826
]
Sreenath Somarajapuram commented on YARN-6278:
--
The changes looks good to me.
> -Pyarn-ui build seems broken in trunk
> -
>
> Key: YARN-6278
> URL: https://issues.apache.org/jira/browse/YARN-6278
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Sunil G
>Assignee: Sunil G
>Priority: Critical
> Attachments: YARN-6278.0001.patch
>
>
> Link to the error is
> [here|https://builds.apache.org/job/PreCommit-HDFS-Build/18535/artifact/patchprocess/patch-compile-root.txt]
> {code}
> qunit-notifications#0.1.1 bower_components/qunit-notifications
> [INFO]
> [INFO] --- exec-maven-plugin:1.3.1:exec (ember build) @ hadoop-yarn-ui ---
> /testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/src/main/webapp/node_modules/merge-trees/index.js:33
> class MergeTrees {
> ^
> Unexpected reserved word
> SyntaxError: Unexpected reserved word
> at Module._compile (module.js:439:25)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Module.require (module.js:364:17)
> at require (module.js:380:17)
> at Object.
> (/testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/src/main/webapp/node_modules/broccoli-merge-trees/index.js:2:18)
> at Module._compile (module.js:456:26)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-3698) Make task attempt log files downloadable from all browsers
[
https://issues.apache.org/jira/browse/YARN-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreenath Somarajapuram updated YARN-3698:
-
Summary: Make task attempt log files downloadable from all browsers (was:
Correct make task attempt log files downloadable from all browsers)
> Make task attempt log files downloadable from all browsers
> --
>
> Key: YARN-3698
> URL: https://issues.apache.org/jira/browse/YARN-3698
> Project: Hadoop YARN
> Issue Type: Task
>Reporter: Sreenath Somarajapuram
>
> Please provide a variant of the link with the following headers set, this
> enables direct download of the file across all browsers. Without these we
> cannot provide a cross-browser download links.
> {code}
> Content-Disposition: attachment; filename="attempt-id.log"
> Content-Type of text/plain
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6070) Support substring match in filters
[ https://issues.apache.org/jira/browse/YARN-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-6070: - Description: Current filter functionalities are good, but could be better if it supports substring match. Checked with the HBase guys, and they were of the opinion that its feasible. was: By default the browser prevents accessing resources from multiple domains. In most cases the UIs would be loaded form a domain different from that of timeline server. Hence without CORS support, it would be difficult for the UIs to load data from timeline v2. YARN-2277 must provide more info on the implementation. Summary: Support substring match in filters (was: CORS support in timeline v2) > Support substring match in filters > -- > > Key: YARN-6070 > URL: https://issues.apache.org/jira/browse/YARN-6070 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelinereader >Reporter: Sreenath Somarajapuram > > Current filter functionalities are good, but could be better if it supports > substring match. > Checked with the HBase guys, and they were of the opinion that its feasible. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6070) CORS support in timeline v2
Sreenath Somarajapuram created YARN-6070: Summary: CORS support in timeline v2 Key: YARN-6070 URL: https://issues.apache.org/jira/browse/YARN-6070 Project: Hadoop YARN Issue Type: Sub-task Components: timelinereader Reporter: Sreenath Somarajapuram By default the browser prevents accessing resources from multiple domains. In most cases the UIs would be loaded form a domain different from that of timeline server. Hence without CORS support, it would be difficult for the UIs to load data from timeline v2. YARN-2277 must provide more info on the implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-6069) CORS support in timeline v2
Sreenath Somarajapuram created YARN-6069: Summary: CORS support in timeline v2 Key: YARN-6069 URL: https://issues.apache.org/jira/browse/YARN-6069 Project: Hadoop YARN Issue Type: Sub-task Components: timelinereader Reporter: Sreenath Somarajapuram By default the browser prevents accessing resources from multiple domains. In most cases the UIs would be loaded form a domain different from that of timeline server. Hence without CORS support, it would be difficult for the UIs to load data from timeline v2. YARN-2277 must provide more info on the implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6003) yarn-ui build failure caused by debug 2.4.0
[
https://issues.apache.org/jira/browse/YARN-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753808#comment-15753808
]
Sreenath Somarajapuram commented on YARN-6003:
--
It because npm uses semantic versioning (semver) rules and the dependencies are
not locked. Semver relies on package developers to not making mistakes, and
here we stumbled upon a package with a bug.
Best option to fix this issue would to move to yarn package manager instead of
npm. It also comes with added advantages like faster build time & offline build
support.
A patch for the same is under investigation.
> yarn-ui build failure caused by debug 2.4.0
> ---
>
> Key: YARN-6003
> URL: https://issues.apache.org/jira/browse/YARN-6003
> Project: Hadoop YARN
> Issue Type: Bug
> Components: build, yarn-ui-v2
>Reporter: Akira Ajisaka
>Priority: Minor
>
> The recent build failure:
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/255/artifact/out/patch-compile-root.txt
> {noformat}
> /testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/src/main/webapp/node_modules/debug/debug.js:126
> debug.color = selectColor(namespae);
> ^
> ReferenceError: namespae is not defined
> at createDebug
> (/testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/src/main/webapp/node_modules/debug/debug.js:126:29)
> at Object.
> (/testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/src/main/webapp/node_modules/ember-cli/lib/models/project.js:16:43)
> at Module._compile (module.js:456:26)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Module.require (module.js:364:17)
> at require (module.js:380:17)
> at Object.
> (/testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/src/main/webapp/node_modules/ember-cli/lib/cli/index.js:4:21)
> at Module._compile (module.js:456:26)
> {noformat}
> build@2.4.0 is broken. https://github.com/visionmedia/debug/issues/347
> Maybe we need to set the version to 2.4.1 explicitly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-3698) Correct make task attempt log files downloadable from all browsers
[
https://issues.apache.org/jira/browse/YARN-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreenath Somarajapuram updated YARN-3698:
-
Description:
Please provide a variant of the link with the following headers set, this
enables direct download of the file across all browsers. Without these we
cannot provide a cross-browser download links.
{code}
Content-Disposition: attachment; filename="attempt-id.log"
Content-Type of text/plain
{code}
was:
Issue with redirection:
On hitting
{code}http://address:8042/node/containerlogs/container_e13_1448429572030_8751_01_000588/uname/syslog_attempt_1448429572030_8751_6_02_00_0{code}
We are getting redirected to the container logs at
{code}http://address:19888/jobhistory/logs/address:45454/container_e13_1448429572030_8751_01_000588/container_e13_1448429572030_8751_01_000588/uname{code}
The ideal behaviour must be to get the respective attempt log.
Make logs downloadable:
Please provide a variant of the link with the following headers set, this
enables direct download of the file across all browsers. Without these we
cannot provide a cross-browser download links.
{code}
Content-Disposition: attachment; filename="attempt-id.log"
Content-Type of text/plain
{code}
Summary: Correct make task attempt log files downloadable from all
browsers (was: Correct node-manager redirection & make task attempt log files
downloadable from all browsers)
> Correct make task attempt log files downloadable from all browsers
> --
>
> Key: YARN-3698
> URL: https://issues.apache.org/jira/browse/YARN-3698
> Project: Hadoop YARN
> Issue Type: Task
>Reporter: Sreenath Somarajapuram
>
> Please provide a variant of the link with the following headers set, this
> enables direct download of the file across all browsers. Without these we
> cannot provide a cross-browser download links.
> {code}
> Content-Disposition: attachment; filename="attempt-id.log"
> Content-Type of text/plain
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-3698) Correct make task attempt log files downloadable from all browsers
[
https://issues.apache.org/jira/browse/YARN-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729417#comment-15729417
]
Sreenath Somarajapuram commented on YARN-3698:
--
Redirection issue would be tracked on YARN-5957.
> Correct make task attempt log files downloadable from all browsers
> --
>
> Key: YARN-3698
> URL: https://issues.apache.org/jira/browse/YARN-3698
> Project: Hadoop YARN
> Issue Type: Task
>Reporter: Sreenath Somarajapuram
>
> Please provide a variant of the link with the following headers set, this
> enables direct download of the file across all browsers. Without these we
> cannot provide a cross-browser download links.
> {code}
> Content-Disposition: attachment; filename="attempt-id.log"
> Content-Type of text/plain
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5888) [YARN-3368] Improve unit tests for YARN UI
[ https://issues.apache.org/jira/browse/YARN-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722215#comment-15722215 ] Sreenath Somarajapuram commented on YARN-5888: -- - Why is 'config/configs.env' required for test? - Tabs are being used instead of space. - I don't see any major test cases/conditions getting added. - What is the "Test fields" in models supposed to test? - Model is just another object and set & get work irrespective of the field names defined in them. Probably this ticket can be used for making UTs run as expected. And further, test cases for each class can be added under an umbrella in individual tickets. > [YARN-3368] Improve unit tests for YARN UI > -- > > Key: YARN-5888 > URL: https://issues.apache.org/jira/browse/YARN-5888 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn-ui-v2 >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Minor > Attachments: YARN-5888.001.patch > > > - Add missing test cases in new YARN UI > - Fix test cases errors in new YARN UI -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5866) [YARN-3368] Fix few issues reported by jshint in new YARN UI
[
https://issues.apache.org/jira/browse/YARN-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722122#comment-15722122
]
Sreenath Somarajapuram commented on YARN-5866:
--
Looks mostly good to me. One suggestion is that it would be better to comment
the function arguments instead of removing them. This would maintain code
readability.
{code}
urlForFindRecord(id /*, modelName, snapshot*/) {
{code}
> [YARN-3368] Fix few issues reported by jshint in new YARN UI
>
>
> Key: YARN-5866
> URL: https://issues.apache.org/jira/browse/YARN-5866
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn-ui-v2
>Reporter: Akhil PB
>Assignee: Akhil PB
> Attachments: YARN-5866.001.patch, YARN-5866.002.patch
>
>
> There are few minor issues reported by jshint (javascript lint tool).
> This jira is to track and fix those issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5868) pre-commit build shows random error from npm plugin related to yarn ui
[
https://issues.apache.org/jira/browse/YARN-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657728#comment-15657728
]
Sreenath Somarajapuram commented on YARN-5868:
--
[~sunilg] Please try upgrading the node version instead of 'npm cache clean',
and check if that helps. Probably something like.
{code}
v5.7.1
3.6.0
{code}
> pre-commit build shows random error from npm plugin related to yarn ui
> --
>
> Key: YARN-5868
> URL: https://issues.apache.org/jira/browse/YARN-5868
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn-ui-v2
>Reporter: Sunil G
>Assignee: Sunil G
> Attachments: YARN-5868.0001.patch, YARN-5868.0002.patch,
> YARN-5868.0003.patch
>
>
> As per below report
> https://builds.apache.org/job/PreCommit-HDFS-Build/17517/artifact/patchprocess/patch-compile-root.txt
> there s a random issue generated by 'npm install' during build.
> This jira is to track the same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5779) [YARN-3368] Document limits/notes of the new YARN UI
[ https://issues.apache.org/jira/browse/YARN-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15615268#comment-15615268 ] Sreenath Somarajapuram commented on YARN-5779: -- +1 Committing > [YARN-3368] Document limits/notes of the new YARN UI > > > Key: YARN-5779 > URL: https://issues.apache.org/jira/browse/YARN-5779 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Wangda Tan > Fix For: YARN-3368 > > Attachments: YARN-5779-YARN-3368.01.patch, > YARN-5779-YARN-3368.02.patch, YARN-5779-YARN-3368.addendum.1.patch > > > For example, we don't make sure it's able to run on security enabled > environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5785) [YARN-3368] Accessing applications and containers list from Node page is throwing few exceptions in console
[ https://issues.apache.org/jira/browse/YARN-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5785: - Attachment: YARN-5785-YARN-3368.002.patch Thanks [~akhilpb] [~sunilg] Attaching a fresh patch with some changes in the way we handle urlForQuery in the adapter. Instead of reseting the host for each request, it would be better to modify the url. > [YARN-3368] Accessing applications and containers list from Node page is > throwing few exceptions in console > --- > > Key: YARN-5785 > URL: https://issues.apache.org/jira/browse/YARN-5785 > Project: Hadoop YARN > Issue Type: Sub-task > Components: yarn-ui-v2 >Reporter: Sunil G >Assignee: Akhil PB > Attachments: YARN-5785-YARN-3368.001.patch, > YARN-5785-YARN-3368.002.patch > > > In node page, "List of Applications" and "List of Containers" links are > causing few error logs in console. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - 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-5145) [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
[
https://issues.apache.org/jira/browse/YARN-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576368#comment-15576368
]
Sreenath Somarajapuram edited comment on YARN-5145 at 10/14/16 8:16 PM:
- Minor comment, Ember Logger could be used instead of direct console log.
- Looking at {code}if(address == "0.0.0.0") {{code}, just wondering if we could
have condition where the addres comes as localhost or 127.0.0.1
was (Author: sreenath):
- Minor comment, Ember Logger could be used instead of direct console.
- Looking at {code}if(address == "0.0.0.0") {{code}, just wondering if we could
have condition where the addres comes as localhost or 127.0.0.1
> [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
> -
>
> Key: YARN-5145
> URL: https://issues.apache.org/jira/browse/YARN-5145
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Wangda Tan
>Assignee: Sunil G
> Attachments: 0001-YARN-5145-Run-NewUI-WithOldPort-POC.patch,
> YARN-5145-YARN-3368.01.patch, YARN-5145-YARN-3368.02.patch,
> YARN-5145-YARN-3368.03.patch, YARN-5145-YARN-3368.04.patch,
> newUIInOldRMWebServer.png
>
>
> Existing YARN UI configuration is under Hadoop package's directory:
> $HADOOP_PREFIX/share/hadoop/yarn/webapps/, we should move it to
> $HADOOP_CONF_DIR like other configurations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5145) [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
[
https://issues.apache.org/jira/browse/YARN-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15576368#comment-15576368
]
Sreenath Somarajapuram commented on YARN-5145:
--
- Minor comment, Ember Logger could be used instead of direct console.
- Looking at {code}if(address == "0.0.0.0") {{code}, just wondering if we could
have condition where the addres comes as localhost or 127.0.0.1
> [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
> -
>
> Key: YARN-5145
> URL: https://issues.apache.org/jira/browse/YARN-5145
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Wangda Tan
>Assignee: Sunil G
> Attachments: 0001-YARN-5145-Run-NewUI-WithOldPort-POC.patch,
> YARN-5145-YARN-3368.01.patch, YARN-5145-YARN-3368.02.patch,
> YARN-5145-YARN-3368.03.patch, YARN-5145-YARN-3368.04.patch,
> newUIInOldRMWebServer.png
>
>
> Existing YARN UI configuration is under Hadoop package's directory:
> $HADOOP_PREFIX/share/hadoop/yarn/webapps/, we should move it to
> $HADOOP_CONF_DIR like other configurations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5145) [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
[ https://issues.apache.org/jira/browse/YARN-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522518#comment-15522518 ] Sreenath Somarajapuram commented on YARN-5145: -- bq. configuration (timeline or others etc) from new REST api Already /conf is working, guess we just need to use that. bq. Its better we can some how run new UI on another port In a case the UI must be server from a different port, say http://RM:8089:/cluster, just provide a http://RM:8089/conf (An alias if http://RM:8088/conf) and things would be well and good. > [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR > - > > Key: YARN-5145 > URL: https://issues.apache.org/jira/browse/YARN-5145 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Kai Sasaki > Attachments: YARN-5145-YARN-3368.01.patch > > > Existing YARN UI configuration is under Hadoop package's directory: > $HADOOP_PREFIX/share/hadoop/yarn/webapps/, we should move it to > $HADOOP_CONF_DIR like other configurations. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5668) Support content-type: application/json in RM's /conf endpoint
[ https://issues.apache.org/jira/browse/YARN-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5668: - Description: - Right now all requests send to RM's /conf endpoint is responded with xml data. Would be great if the endpoint checks the request headers, and return data in JSON format for content-type: application/json. - This would make accessing configurations from web UIs easier. Else it would add an extra UI dependency on any of the xml libraries. was: Right now all requests send to RM's /conf endpoint is responded with xml data. Would be great if the endpoint checks the request headers, and return data in JSON format for content-type: application/json. Summary: Support content-type: application/json in RM's /conf endpoint (was: content-type: application/json support in RM's /conf endpoint) > Support content-type: application/json in RM's /conf endpoint > - > > Key: YARN-5668 > URL: https://issues.apache.org/jira/browse/YARN-5668 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Sreenath Somarajapuram > > - Right now all requests send to RM's /conf endpoint is responded with xml > data. Would be great if the endpoint checks the request headers, and return > data in JSON format for content-type: application/json. > - This would make accessing configurations from web UIs easier. Else it would > add an extra UI dependency on any of the xml libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5145) [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
[ https://issues.apache.org/jira/browse/YARN-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522419#comment-15522419 ] Sreenath Somarajapuram commented on YARN-5145: -- [~leftnoteasy] [~cheersyang] Adding to that, would be great if /conf support content-type, JSON. Have created YARN-5668 for the same. > [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR > - > > Key: YARN-5145 > URL: https://issues.apache.org/jira/browse/YARN-5145 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Kai Sasaki > Attachments: YARN-5145-YARN-3368.01.patch > > > Existing YARN UI configuration is under Hadoop package's directory: > $HADOOP_PREFIX/share/hadoop/yarn/webapps/, we should move it to > $HADOOP_CONF_DIR like other configurations. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5668) content-type: application/json support in RM's /conf endpoint
[ https://issues.apache.org/jira/browse/YARN-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5668: - Description: Right now all requests send to RM's /conf endpoint is responded with xml data. Would be great if the endpoint checks the request headers, and return data in JSON format for content-type: application/json. was: Right now all requests send to /conf is returned with xml data. Would be great if the endpoint checks the request headers, and return data in JSON format for content-type: application/json. Summary: content-type: application/json support in RM's /conf endpoint (was: content-type: application/json support in /conf endpoint) > content-type: application/json support in RM's /conf endpoint > - > > Key: YARN-5668 > URL: https://issues.apache.org/jira/browse/YARN-5668 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Sreenath Somarajapuram > > Right now all requests send to RM's /conf endpoint is responded with xml > data. Would be great if the endpoint checks the request headers, and return > data in JSON format for content-type: application/json. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5668) content-type: application/json support in /conf endpoint
Sreenath Somarajapuram created YARN-5668: Summary: content-type: application/json support in /conf endpoint Key: YARN-5668 URL: https://issues.apache.org/jira/browse/YARN-5668 Project: Hadoop YARN Issue Type: Improvement Reporter: Sreenath Somarajapuram Right now all requests send to /conf is returned with xml data. Would be great if the endpoint checks the request headers, and return data in JSON format for content-type: application/json. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5145) [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
[ https://issues.apache.org/jira/browse/YARN-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15520595#comment-15520595 ] Sreenath Somarajapuram commented on YARN-5145: -- bq. not sure if it is possible to run two HTTP server on the same port Not sure why we need two servers. Old UI had various static assets like the hadoop-st.png logo file, yarn.css and various js files. Similar to them all our new UI files are static assets, and we just need to server them over '/ui' end point when enabled by the user. > [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR > - > > Key: YARN-5145 > URL: https://issues.apache.org/jira/browse/YARN-5145 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Kai Sasaki > Attachments: YARN-5145-YARN-3368.01.patch > > > Existing YARN UI configuration is under Hadoop package's directory: > $HADOOP_PREFIX/share/hadoop/yarn/webapps/, we should move it to > $HADOOP_CONF_DIR like other configurations. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5145) [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
[ https://issues.apache.org/jira/browse/YARN-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15518523#comment-15518523 ] Sreenath Somarajapuram commented on YARN-5145: -- [~leftnoteasy] Like the existing UI that is available at http://RM:8088/cluster endpoint, wouldn't the new UI be hosted under 8088 itself? In JS the domain an UI is loaded from is available @ window.location.host. In other words, if the UI is loaded from http://:/ui, the UI can get the required details from window.location.host (which would be http://:), and connect to http://:/conf. > [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR > - > > Key: YARN-5145 > URL: https://issues.apache.org/jira/browse/YARN-5145 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Kai Sasaki > Attachments: YARN-5145-YARN-3368.01.patch > > > Existing YARN UI configuration is under Hadoop package's directory: > $HADOOP_PREFIX/share/hadoop/yarn/webapps/, we should move it to > $HADOOP_CONF_DIR like other configurations. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5145) [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR
[ https://issues.apache.org/jira/browse/YARN-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15517498#comment-15517498 ] Sreenath Somarajapuram commented on YARN-5145: -- [~leftnoteasy] config.env, default-config.js and environment.js were initially created with different purposes. # config.env - For configuring host URLs and other values respective to the machine the UI is hosted in. It would be a separate file, and wont be imploded by the build script. Hence when the UI is hosted in tomcat or some similar server, the user can go and configure the UI. In other words, this file is used to configure UI in the deployment phase. # default-config.js - Contains default values of the above + other constants internal to the UI (Like REST end point namespaces). This would be imploded and minified by the build script. Hence this file can be changed only before the build, or in the development phase. # environment.js - This is Ember's standard file, and contain Ember related environment variables. They define how ember works. In short. If we remove config.env. Someone who want to host our UI war in his/her tomcat or similar servers would find it hard to get the UI working. Now accessing the configuration: # Production - UI hosted in RM : As mentioned by [~cheersyang], the UI can load configurations from RM's conf endpoint. # Production - UI hosted in a web server (tomcat) : config.env can be used to configure the host URLs. (HADOOP_CONF_DIR could be out of reach as the machine its hosted in need not be even a part of the cluster) # Production - wrapped : Things would be different if it is viewed inside other web interfaces like Ambari. We would have to take the configurations from REST end points provided by the respective interfaces. Guess that is out of scope now. # Development : config.env can be used to configure the host URLs. > [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR > - > > Key: YARN-5145 > URL: https://issues.apache.org/jira/browse/YARN-5145 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Kai Sasaki > Attachments: YARN-5145-YARN-3368.01.patch > > > Existing YARN UI configuration is under Hadoop package's directory: > $HADOOP_PREFIX/share/hadoop/yarn/webapps/, we should move it to > $HADOOP_CONF_DIR like other configurations. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5503) [YARN-3368] Add missing hidden files in webapp folder
[ https://issues.apache.org/jira/browse/YARN-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448777#comment-15448777 ] Sreenath Somarajapuram commented on YARN-5503: -- Regarding test4tests: The patch doesn't add or modify any business logic. So tests are not required. > [YARN-3368] Add missing hidden files in webapp folder > - > > Key: YARN-5503 > URL: https://issues.apache.org/jira/browse/YARN-5503 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5503-YARN-3368-0001.patch, > YARN-5503-YARN-3368-0001.patch, YARN-5503-YARN-3368-0002.patch, > YARN-5503-YARN-3368-0003.patch, YARN-5503-YARN-3368-0004.patch, > YARN-5503-YARN-3368.0005.patch > > > - Feel it might be good to have a readme file with the basic instructions. > - Change package type to war, as ours is a web application > - Just noticed that the hidden files that must be present in the base > directory of ember app, are missing. Most of them are used for configuration, > and when missing the default vakues would be used by ember. > -- They include - .bowerrc, .editorconfig, .ember-cli, .gitignore, .jshintrc, > .travis.yml, .watchmanconfig -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5503) [YARN-3368] Add missing hidden files in webapp folder
[ https://issues.apache.org/jira/browse/YARN-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5503: - Attachment: YARN-5503-YARN-3368-0001.patch Attaching a fresh patch without root level changes. Those will be added as part of YARN-5583. > [YARN-3368] Add missing hidden files in webapp folder > - > > Key: YARN-5503 > URL: https://issues.apache.org/jira/browse/YARN-5503 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5503-YARN-3368-0001.patch, > YARN-5503-YARN-3368-0001.patch, YARN-5503-YARN-3368-0002.patch, > YARN-5503-YARN-3368-0003.patch, YARN-5503-YARN-3368-0004.patch, > YARN-5503-YARN-3368.0005.patch > > > - Feel it might be good to have a readme file with the basic instructions. > - Change package type to war, as ours is a web application > - Just noticed that the hidden files that must be present in the base > directory of ember app, are missing. Most of them are used for configuration, > and when missing the default vakues would be used by ember. > -- They include - .bowerrc, .editorconfig, .ember-cli, .gitignore, .jshintrc, > .travis.yml, .watchmanconfig -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5503) [YARN-3368] Add missing hidden files in webapp folder
[ https://issues.apache.org/jira/browse/YARN-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5503: - Description: - Feel it might be good to have a readme file with the basic instructions. - Change package type to war, as ours is a web application - Just noticed that the hidden files that must be present in the base directory of ember app, are missing. Most of them are used for configuration, and when missing the default vakues would be used by ember. -- They include - .bowerrc, .editorconfig, .ember-cli, .gitignore, .jshintrc, .travis.yml, .watchmanconfig was: - Feel it might be good to have a readme file with the basic instructions. - Just noticed that the hidden files that must be present in the base directory of ember app, are missing. Most of them are used for configuration, and when missing the default vakues would be used by ember. -- They include - .bowerrc, .editorconfig, .ember-cli, .gitignore, .jshintrc, .travis.yml, .watchmanconfig > [YARN-3368] Add missing hidden files in webapp folder > - > > Key: YARN-5503 > URL: https://issues.apache.org/jira/browse/YARN-5503 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5503-YARN-3368-0001.patch, > YARN-5503-YARN-3368-0002.patch, YARN-5503-YARN-3368-0003.patch, > YARN-5503-YARN-3368-0004.patch, YARN-5503-YARN-3368.0005.patch > > > - Feel it might be good to have a readme file with the basic instructions. > - Change package type to war, as ours is a web application > - Just noticed that the hidden files that must be present in the base > directory of ember app, are missing. Most of them are used for configuration, > and when missing the default vakues would be used by ember. > -- They include - .bowerrc, .editorconfig, .ember-cli, .gitignore, .jshintrc, > .travis.yml, .watchmanconfig -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5583) [YARN-3368] Fix paths in .gitignore
[ https://issues.apache.org/jira/browse/YARN-5583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5583: - Attachment: YARN-5583-YARN-3368-0001.patch [~sunilg] [~wangda] [~vvasudev] Please help with this root level patch. This would trigger complete build, and might cause unrelated pre-commit failures. > [YARN-3368] Fix paths in .gitignore > --- > > Key: YARN-5583 > URL: https://issues.apache.org/jira/browse/YARN-5583 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5583-YARN-3368-0001.patch > > > npm-debug.log & testem.log paths are mentioned wrong. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5583) [YARN-3368] Fix paths in .gitignore
Sreenath Somarajapuram created YARN-5583: Summary: [YARN-3368] Fix paths in .gitignore Key: YARN-5583 URL: https://issues.apache.org/jira/browse/YARN-5583 Project: Hadoop YARN Issue Type: Sub-task Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram npm-debug.log & testem.log paths are mentioned wrong. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5504) [YARN-3368] Fix the YARN UI build
[ https://issues.apache.org/jira/browse/YARN-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435676#comment-15435676 ] Sreenath Somarajapuram commented on YARN-5504: -- - Have added -Dkeep-ui-build-cache as discussed. - I doubt if the UTs were functional as the requisites for UTs are not available. Can enable them sometime later, but for the time being lets keep them dormant. > [YARN-3368] Fix the YARN UI build > - > > Key: YARN-5504 > URL: https://issues.apache.org/jira/browse/YARN-5504 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5504-YARN-3368-0001.patch, > YARN-5504-YARN-3368-0002.patch > > > - Disable tests as we don't have UTs. > - Disable lint & hint as they are not followed by the current codebase, and > are throwing build errors. > - Disable clearing of UI package on building, so that n/w is required only in > the first build. > - Remove duplicate bower installs. > -Change the default packaging.type to 'war' as our UI is a Web application- - > Will keep it in the profile > -Final war should just contain the end result of the build and not all files- > [~wangda] [~vinodkv] [~sunilg] please share your thoughts. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5504) [YARN-3368] Fix the YARN UI build
[ https://issues.apache.org/jira/browse/YARN-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5504: - Description: - Disable tests as we don't have UTs. - Disable lint & hint as they are not followed by the current codebase, and are throwing build errors. - Disable clearing of UI package on building, so that n/w is required only in the first build. - Remove duplicate bower installs. -Change the default packaging.type to 'war' as our UI is a Web application- - Will keep it in the profile -Final war should just contain the end result of the build and not all files- [~wangda] [~vinodkv] [~sunilg] please share your thoughts. was: - Disable tests as we don't have UTs. - Disable lint & hint as they are not followed by the current codebase, and are throwing build errors. - Disable clearing of UI package on building, so that n/w is required only in the first build. - Remove duplicate bower installs. - Change the default packaging.type to 'war' as our UI is a Web application- - Will keep it in the profile - Final war should just contain the end result of the build and not all files- [~wangda] [~vinodkv] [~sunilg] please share your thoughts. > [YARN-3368] Fix the YARN UI build > - > > Key: YARN-5504 > URL: https://issues.apache.org/jira/browse/YARN-5504 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5504-YARN-3368-0001.patch, > YARN-5504-YARN-3368-0002.patch > > > - Disable tests as we don't have UTs. > - Disable lint & hint as they are not followed by the current codebase, and > are throwing build errors. > - Disable clearing of UI package on building, so that n/w is required only in > the first build. > - Remove duplicate bower installs. > -Change the default packaging.type to 'war' as our UI is a Web application- - > Will keep it in the profile > -Final war should just contain the end result of the build and not all files- > [~wangda] [~vinodkv] [~sunilg] please share your thoughts. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5504) [YARN-3368] Fix the YARN UI build
[ https://issues.apache.org/jira/browse/YARN-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5504: - Attachment: YARN-5504-YARN-3368-0002.patch Attaching a second patch with some of the comments addressed. > [YARN-3368] Fix the YARN UI build > - > > Key: YARN-5504 > URL: https://issues.apache.org/jira/browse/YARN-5504 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5504-YARN-3368-0001.patch, > YARN-5504-YARN-3368-0002.patch > > > - Disable tests as we don't have UTs. > - Disable lint & hint as they are not followed by the current codebase, and > are throwing build errors. > - Disable clearing of UI package on building, so that n/w is required only in > the first build. > - Remove duplicate bower installs. > - Change the default packaging.type to 'war' as our UI is a Web application- > - Will keep it in the profile > - Final war should just contain the end result of the build and not all files- > [~wangda] [~vinodkv] [~sunilg] please share your thoughts. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5503) [YARN-3368] Add missing hidden files in webapp folder
[ https://issues.apache.org/jira/browse/YARN-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5503: - Summary: [YARN-3368] Add missing hidden files in webapp folder (was: [YARN-3368] Add readme and other missing hidden files in webapp folder) > [YARN-3368] Add missing hidden files in webapp folder > - > > Key: YARN-5503 > URL: https://issues.apache.org/jira/browse/YARN-5503 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5503-YARN-3368-0001.patch, > YARN-5503-YARN-3368-0002.patch, YARN-5503-YARN-3368-0003.patch, > YARN-5503-YARN-3368-0004.patch > > > - Feel it might be good to have a readme file with the basic instructions. > - Just noticed that the hidden files that must be present in the base > directory of ember app, are missing. Most of them are used for configuration, > and when missing the default vakues would be used by ember. > -- They include - .bowerrc, .editorconfig, .ember-cli, .gitignore, .jshintrc, > .travis.yml, .watchmanconfig -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5503) [YARN-3368] Add readme and other missing hidden files in webapp folder
[ https://issues.apache.org/jira/browse/YARN-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5503: - Attachment: YARN-5503-YARN-3368-0004.patch Attaching patch 4 without readme, as that must go into the wiki. > [YARN-3368] Add readme and other missing hidden files in webapp folder > -- > > Key: YARN-5503 > URL: https://issues.apache.org/jira/browse/YARN-5503 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5503-YARN-3368-0001.patch, > YARN-5503-YARN-3368-0002.patch, YARN-5503-YARN-3368-0003.patch, > YARN-5503-YARN-3368-0004.patch > > > - Feel it might be good to have a readme file with the basic instructions. > - Just noticed that the hidden files that must be present in the base > directory of ember app, are missing. Most of them are used for configuration, > and when missing the default vakues would be used by ember. > -- They include - .bowerrc, .editorconfig, .ember-cli, .gitignore, .jshintrc, > .travis.yml, .watchmanconfig -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5558) YARN Timeline Server and RM - Return status code 401(Unauthorized) if the user is not in ACL
Sreenath Somarajapuram created YARN-5558: Summary: YARN Timeline Server and RM - Return status code 401(Unauthorized) if the user is not in ACL Key: YARN-5558 URL: https://issues.apache.org/jira/browse/YARN-5558 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager, timelineserver Reporter: Sreenath Somarajapuram It would be better if YARN Timeline Server and RM could return status code 401(Unauthorized) if the user is not in ACL - Currently, if user is not in ACL, the REST APIs return status code 404 (Not Found). - This makes it hard for the requester to determine if it was a permission issue, or the data was actually missing. - Returning 401 would state that the user is not authorised to access the requested resource. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5503) [YARN-3368] Add readme and other missing hidden files in webapp folder
[ https://issues.apache.org/jira/browse/YARN-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5503: - Attachment: YARN-5503-YARN-3368-0003.patch Thanks [~wangda] Attaching a patch with the comments addressed. - I have removed .travis.yml. If required we can add them later when UTs are added. - [~sunilg] Thansk for confirming the war change - Minor changes were made to .gitignore file in top-level - Other dot-files are for configuring the packages that we use for development, so guess its better to have those. - I haven't touched YarnUI2.md as that talks mostly from a deployment perspective. Should I modify YarnUI2.md instead of adding README.md? > [YARN-3368] Add readme and other missing hidden files in webapp folder > -- > > Key: YARN-5503 > URL: https://issues.apache.org/jira/browse/YARN-5503 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5503-YARN-3368-0001.patch, > YARN-5503-YARN-3368-0002.patch, YARN-5503-YARN-3368-0003.patch > > > - Feel it might be good to have a readme file with the basic instructions. > - Just noticed that the hidden files that must be present in the base > directory of ember app, are missing. Most of them are used for configuration, > and when missing the default vakues would be used by ember. > -- They include - .bowerrc, .editorconfig, .ember-cli, .gitignore, .jshintrc, > .travis.yml, .watchmanconfig -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5504) [YARN-3368] Fix the YARN UI build
[ https://issues.apache.org/jira/browse/YARN-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422543#comment-15422543 ] Sreenath Somarajapuram commented on YARN-5504: -- bq. I have doubt. In which all cases, we need to clean node_modules etc. Do we have a case where we must delete this, and if so, how we could do same from maven (may be --force-clean). Thoughts? - Do we have a case: We could, I have observed permission issues when multiple users try to build on the same codebase. - Guess force-clean, could be a good addition. bq. Instead of skipping clean up directories, can we leverage tools like https://www.npmjs.com/package/npm-cache to install from cache? I think it doesn't look good if we do not clean up temp npm files. And it brings troubles to developers (see a lot of git untracked files) when they switching Hadoop branches. - npm-cache is an npm package like other items in node_modules, so the question is, where would the npm-cached be cached? - Currently npm install works as the frontend-maven-plugin can download, cache and use node, NPM, bower and few other build tools. - Also in effect, npm-cached looks similar to not deleting the directories. - Now regarding the untracked file - Ideally both node_modules and bower_components must be part of .gitignore. And if we move to a branch without hadoop-yarn-ui, then doesn't the list go only till hadoop-yarn-ui? bq. I think we should have few UTs, adding more tests is very important for better quality. Is there any benefit we can get from disabling UTs? - Totally agree that UTs are required. But ember uses PhantomJs to run the integration tests, and Phantom JS have some issue when the build is run from behind a proxy. Considering that some of our builds run behind a cache proxy, this might cause issues. We are facing this in Tez. So guess it would be better to add them once PhantomJS dependency issues are fixed. - Also it might be better to add them after hinting is enabled. And that is going to be a big change. > [YARN-3368] Fix the YARN UI build > - > > Key: YARN-5504 > URL: https://issues.apache.org/jira/browse/YARN-5504 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5504-YARN-3368-0001.patch > > > - Disable tests as we don't have UTs. > - Disable lint & hint as they are not followed by the current codebase, and > are throwing build errors. > - Disable clearing of UI package on building, so that n/w is required only in > the first build. > - Remove duplicate bower installs. > - Change the default packaging.type to 'war' as our UI is a Web application- > - Will keep it in the profile > - Final war should just contain the end result of the build and not all files- > [~wangda] [~vinodkv] [~sunilg] please share your thoughts. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5503) [YARN-3368] Add readme and other missing hidden files in webapp folder
[ https://issues.apache.org/jira/browse/YARN-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5503: - Attachment: YARN-5503-YARN-3368-0002.patch Attaching a second patch with with a small change in README. Added `-Pyarn-ui` in the build command. > [YARN-3368] Add readme and other missing hidden files in webapp folder > -- > > Key: YARN-5503 > URL: https://issues.apache.org/jira/browse/YARN-5503 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5503-YARN-3368-0001.patch, > YARN-5503-YARN-3368-0002.patch > > > - Feel it might be good to have a readme file with the basic instructions. > - Just noticed that the hidden files that must be present in the base > directory of ember app, are missing. Most of them are used for configuration, > and when missing the default vakues would be used by ember. > -- They include - .bowerrc, .editorconfig, .ember-cli, .gitignore, .jshintrc, > .travis.yml, .watchmanconfig -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5504) [YARN-3368] Fix the YARN UI build
[ https://issues.apache.org/jira/browse/YARN-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5504: - Attachment: YARN-5504-YARN-3368-0001.patch [~leftnoteasy] Please review. > [YARN-3368] Fix the YARN UI build > - > > Key: YARN-5504 > URL: https://issues.apache.org/jira/browse/YARN-5504 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5504-YARN-3368-0001.patch > > > - Disable tests as we don't have UTs. > - Disable lint & hint as they are not followed by the current codebase, and > are throwing build errors. > - Disable clearing of UI package on building, so that n/w is required only in > the first build. > - Remove duplicate bower installs. > -Change the default packaging.type to 'war' as our UI is a Web application- - > Will keep it in the profile > -Final war should just contain the end result of the build and not all files- > [~wangda] [~vinodkv] [~sunilg] please share your thoughts. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5504) [YARN-3368] Fix the YARN UI build
[ https://issues.apache.org/jira/browse/YARN-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5504: - Description: - Disable tests as we don't have UTs. - Disable lint & hint as they are not followed by the current codebase, and are throwing build errors. - Disable clearing of UI package on building, so that n/w is required only in the first build. - Remove duplicate bower installs. -Change the default packaging.type to 'war' as our UI is a Web application- - Will keep it in the profile -Final war should just contain the end result of the build and not all files- [~wangda] [~vinodkv] [~sunilg] please share your thoughts. was: - Disable tests as we don't have UTs. - Disable lint & hint as they are not followed by the current codebase, and are throwing build errors. - Disable clearing of UI package on building, so that n/w is required only in the first build. -Change the default packaging.type to 'war' as our UI is a Web application- - Will keep it in the profile -Final war should just contain the end result of the build and not all files- [~wangda] [~vinodkv] [~sunilg] please share your thoughts. > [YARN-3368] Fix the YARN UI build > - > > Key: YARN-5504 > URL: https://issues.apache.org/jira/browse/YARN-5504 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > > - Disable tests as we don't have UTs. > - Disable lint & hint as they are not followed by the current codebase, and > are throwing build errors. > - Disable clearing of UI package on building, so that n/w is required only in > the first build. > - Remove duplicate bower installs. > -Change the default packaging.type to 'war' as our UI is a Web application- - > Will keep it in the profile > -Final war should just contain the end result of the build and not all files- > [~wangda] [~vinodkv] [~sunilg] please share your thoughts. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5504) [YARN-3368] Fix the YARN UI build
[ https://issues.apache.org/jira/browse/YARN-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5504: - Description: - Disable tests as we don't have UTs. - Disable lint & hint as they are not followed by the current codebase, and are throwing build errors. - Disable clearing of UI package on building, so that n/w is required only in the first build. -Change the default packaging.type to 'war' as our UI is a Web application- - Will keep it in the profile -Final war should just contain the end result of the build and not all files- [~wangda] [~vinodkv] [~sunilg] please share your thoughts. was: - Disable tests as we don't have UTs. - Disable lint & hint as they are not followed by the current codebase, and are throwing build errors. - Disable clearing of UI package on building, so that n/w is required only in the first build. -Change the default packaging.type to 'war' as our UI is a Web application- Will keep it in the profile -Final war should just contain the end result of the build and not all files- [~wangda] [~vinodkv] [~sunilg] please share your thoughts. > [YARN-3368] Fix the YARN UI build > - > > Key: YARN-5504 > URL: https://issues.apache.org/jira/browse/YARN-5504 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > > - Disable tests as we don't have UTs. > - Disable lint & hint as they are not followed by the current codebase, and > are throwing build errors. > - Disable clearing of UI package on building, so that n/w is required only in > the first build. > -Change the default packaging.type to 'war' as our UI is a Web application- - > Will keep it in the profile > -Final war should just contain the end result of the build and not all files- > [~wangda] [~vinodkv] [~sunilg] please share your thoughts. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5504) [YARN-3368] Fix the YARN UI build
[ https://issues.apache.org/jira/browse/YARN-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5504: - Description: - Disable tests as we don't have UTs. - Disable lint & hint as they are not followed by the current codebase, and are throwing build errors. - Disable clearing of UI package on building, so that n/w is required only in the first build. -Change the default packaging.type to 'war' as our UI is a Web application- Will keep it in the profile -Final war should just contain the end result of the build and not all files- [~wangda] [~vinodkv] [~sunilg] please share your thoughts. was: - Disable tests as we don't have UTs. - Disable lint & hint as they are not followed by the current codebase, and are throwing build errors. - Disable clearing of UI package on building, so that n/w is required only in the first build. - Change the default packaging.type to 'war' as our UI is a Web application. - Final war should just contain the end result of the build and not all files. [~wangda] [~vinodkv] [~sunilg] please share your thoughts. > [YARN-3368] Fix the YARN UI build > - > > Key: YARN-5504 > URL: https://issues.apache.org/jira/browse/YARN-5504 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > > - Disable tests as we don't have UTs. > - Disable lint & hint as they are not followed by the current codebase, and > are throwing build errors. > - Disable clearing of UI package on building, so that n/w is required only in > the first build. > -Change the default packaging.type to 'war' as our UI is a Web application- > Will keep it in the profile > -Final war should just contain the end result of the build and not all files- > [~wangda] [~vinodkv] [~sunilg] please share your thoughts. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5504) [YARN-3368] Fix the YARN UI build
[ https://issues.apache.org/jira/browse/YARN-5504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5504: - Issue Type: Sub-task (was: Bug) Parent: YARN-3368 > [YARN-3368] Fix the YARN UI build > - > > Key: YARN-5504 > URL: https://issues.apache.org/jira/browse/YARN-5504 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > > - Disable tests as we don't have UTs. > - Disable lint & hint as they are not followed by the current codebase, and > are throwing build errors. > - Disable clearing of UI package on building, so that n/w is required only in > the first build. > - Change the default packaging.type to 'war' as our UI is a Web application. > - Final war should just contain the end result of the build and not all files. > [~wangda] [~vinodkv] [~sunilg] please share your thoughts. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5504) [YARN-3368] Fix the YARN UI build
Sreenath Somarajapuram created YARN-5504: Summary: [YARN-3368] Fix the YARN UI build Key: YARN-5504 URL: https://issues.apache.org/jira/browse/YARN-5504 Project: Hadoop YARN Issue Type: Bug Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram - Disable tests as we don't have UTs. - Disable lint & hint as they are not followed by the current codebase, and are throwing build errors. - Disable clearing of UI package on building, so that n/w is required only in the first build. - Change the default packaging.type to 'war' as our UI is a Web application. - Final war should just contain the end result of the build and not all files. [~wangda] [~vinodkv] [~sunilg] please share your thoughts. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5503) [YARN-3368] Add readme and other missing hidden files in webapp folder
[ https://issues.apache.org/jira/browse/YARN-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5503: - Attachment: YARN-5503-YARN-3368-0001.patch [~wangda] Attaching a patch with the missing files and readme. Please review. > [YARN-3368] Add readme and other missing hidden files in webapp folder > -- > > Key: YARN-5503 > URL: https://issues.apache.org/jira/browse/YARN-5503 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: YARN-5503-YARN-3368-0001.patch > > > - Feel it might be good to have a readme file with the basic instructions. > - Just noticed that the hidden files that must be present in the base > directory of ember app, are missing. Most of them are used for configuration, > and when missing the default vakues would be used by ember. > -- They include - .bowerrc, .editorconfig, .ember-cli, .gitignore, .jshintrc, > .travis.yml, .watchmanconfig -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5503) [YARN-3368] Add readme and other missing hidden files in webapp folder
Sreenath Somarajapuram created YARN-5503: Summary: [YARN-3368] Add readme and other missing hidden files in webapp folder Key: YARN-5503 URL: https://issues.apache.org/jira/browse/YARN-5503 Project: Hadoop YARN Issue Type: Sub-task Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram - Feel it might be good to have a readme file with the basic instructions. - Just noticed that the hidden files that must be present in the base directory of ember app, are missing. Most of them are used for configuration, and when missing the default vakues would be used by ember. -- They include - .bowerrc, .editorconfig, .ember-cli, .gitignore, .jshintrc, .travis.yml, .watchmanconfig -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-5147) [YARN-3368] Showing JMX metrics for YARN servers on new YARN UI
[ https://issues.apache.org/jira/browse/YARN-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram reassigned YARN-5147: Assignee: Sreenath Somarajapuram (was: Sunil G) > [YARN-3368] Showing JMX metrics for YARN servers on new YARN UI > --- > > Key: YARN-5147 > URL: https://issues.apache.org/jira/browse/YARN-5147 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Sreenath Somarajapuram > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5334) [YARN-3368] Introduce REFRESH button in various UI pages
[ https://issues.apache.org/jira/browse/YARN-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5334: - Attachment: YARN-5334-YARN-3368-0002.patch [~sunilg] - Attaching a fresh patch with blind unload of all loaded entities, hope it makes the refresh functionality fool-proof. Additional changes to minimize code duplication: - Created an abstract route class for adding common route functionalities. - Created a breadcrumb-bar component, with breadcrumb and refresh button. > [YARN-3368] Introduce REFRESH button in various UI pages > > > Key: YARN-5334 > URL: https://issues.apache.org/jira/browse/YARN-5334 > Project: Hadoop YARN > Issue Type: Sub-task > Components: webapp >Reporter: Sunil G >Assignee: Sreenath Somarajapuram > Attachments: YARN-5334-YARN-3368-0001.patch, > YARN-5334-YARN-3368-0002.patch > > > It will be better if we have a common Refresh button in all pages to get the > latest information in all tables such as apps/nodes/queue etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5334) [YARN-3368] Introduce REFRESH button in various UI pages
[ https://issues.apache.org/jira/browse/YARN-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407556#comment-15407556 ] Sreenath Somarajapuram commented on YARN-5334: -- Thanks [~sunilg] & [~leftnoteasy] Without unload: Existing record objects would be reused, and only values in them would be updated. With unload: Entity records would be deleted from store and recreated. Our current components are just listening to the record thats passed into it, they don't listen to change in values inside the record. So they would update only when the record change. Unloading and then querying would ensure that the components are provided with new records, and thus we can ensure that they are updating. Current patch, unloads the records only when required. But probably for the time being, we can unload all records to ensure that nothing left behind to refresh. Once the components are made better, we can remove the unloads. But guess that refactoring can be done at a later stage. > [YARN-3368] Introduce REFRESH button in various UI pages > > > Key: YARN-5334 > URL: https://issues.apache.org/jira/browse/YARN-5334 > Project: Hadoop YARN > Issue Type: Sub-task > Components: webapp >Reporter: Sunil G >Assignee: Sreenath Somarajapuram > Attachments: YARN-5334-YARN-3368-0001.patch > > > It will be better if we have a common Refresh button in all pages to get the > latest information in all tables such as apps/nodes/queue etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5334) [YARN-3368] Introduce REFRESH button in various UI pages
[ https://issues.apache.org/jira/browse/YARN-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5334: - Attachment: YARN-5334-YARN-3368-0001.patch [~sunilg] [~leftnoteasy] Please help. > [YARN-3368] Introduce REFRESH button in various UI pages > > > Key: YARN-5334 > URL: https://issues.apache.org/jira/browse/YARN-5334 > Project: Hadoop YARN > Issue Type: Sub-task > Components: webapp >Reporter: Sunil G >Assignee: Sreenath Somarajapuram > Attachments: YARN-5334-YARN-3368-0001.patch > > > It will be better if we have a common Refresh button in all pages to get the > latest information in all tables such as apps/nodes/queue etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5321) [YARN-3368] Add resource usage for application by node managers
[ https://issues.apache.org/jira/browse/YARN-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379130#comment-15379130 ] Sreenath Somarajapuram commented on YARN-5321: -- +1 LGTM Other alignment issues can be dealt with another ticket. > [YARN-3368] Add resource usage for application by node managers > --- > > Key: YARN-5321 > URL: https://issues.apache.org/jira/browse/YARN-5321 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Wangda Tan > Attachments: YARN-5321-YARN-3368-0001.patch, > YARN-5321-YARN-3368.0002.patch, YARN-5321-YARN-3368.003.patch, > YARN-5321-YARN-3368.004.patch, YARN-5321-YARN-3368.005.patch, sample-1.png > > > With this, user can understand distribution of resources allocated to this > application. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5321) [YARN-3368] Add resource usage for application by node managers
[ https://issues.apache.org/jira/browse/YARN-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376618#comment-15376618 ] Sreenath Somarajapuram commented on YARN-5321: -- Few minor observations: # We have some commented code that could be removed. # There are some improvements that could be done on the details page components - Can be done as part a different jira. > [YARN-3368] Add resource usage for application by node managers > --- > > Key: YARN-5321 > URL: https://issues.apache.org/jira/browse/YARN-5321 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Wangda Tan > Attachments: YARN-5321-YARN-3368-0001.patch, > YARN-5321-YARN-3368.0002.patch, YARN-5321-YARN-3368.003.patch, > YARN-5321-YARN-3368.004.patch, sample-1.png > > > With this, user can understand distribution of resources allocated to this > application. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5346) [YARN-3368] Queues page improvements
[ https://issues.apache.org/jira/browse/YARN-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5346: - Summary: [YARN-3368] Queues page improvements (was: [YARN-3368] Queues page improvementS) > [YARN-3368] Queues page improvements > > > Key: YARN-5346 > URL: https://issues.apache.org/jira/browse/YARN-5346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > > Queues page: > - Reorder contents in existing Queues page, and Improve UI components > - On clicking a queue, the user must be taken to the respective queue's > details page. > - Display queue details on mouseover > - The bar and doughnut charts doesn't update on queue change, that needs to > be fixed > Queue details page: > - Add a sub-page for all applications running under the queue -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5347) [YARN-3368] Applications page improvements
[ https://issues.apache.org/jira/browse/YARN-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5347: - Assignee: Sreenath Somarajapuram Summary: [YARN-3368] Applications page improvements (was: [YARN-3368] Applications page improvement) > [YARN-3368] Applications page improvements > -- > > Key: YARN-5347 > URL: https://issues.apache.org/jira/browse/YARN-5347 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > > Applications page: > - Add a "Long running service" sub-page > Application details page: > - Improve the layout > -- Correct the component borders - Remove double border & the extra space > -- Layout "Application Basic Information" vertically > - List attempts under the application as a subpage > - Hide the diagnostics panel when, diagnostics data is not available -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-5348) [YARN-3368] Node details page improvements
[ https://issues.apache.org/jira/browse/YARN-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram reassigned YARN-5348: Assignee: Sreenath Somarajapuram > [YARN-3368] Node details page improvements > -- > > Key: YARN-5348 > URL: https://issues.apache.org/jira/browse/YARN-5348 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > > - Improve the component styling > - Correct padding in Node Information table -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-5344) [YARN-3368] Generic UI improvements
[ https://issues.apache.org/jira/browse/YARN-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram reassigned YARN-5344: Assignee: Sreenath Somarajapuram > [YARN-3368] Generic UI improvements > --- > > Key: YARN-5344 > URL: https://issues.apache.org/jira/browse/YARN-5344 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > > - Add breadcrumps in all pages > - Define a vertical space (to the left) for displaying sub-pages -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Assigned] (YARN-5345) [YARN-3368] Cluster overview page improvements
[ https://issues.apache.org/jira/browse/YARN-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram reassigned YARN-5345: Assignee: Sreenath Somarajapuram > [YARN-3368] Cluster overview page improvements > -- > > Key: YARN-5345 > URL: https://issues.apache.org/jira/browse/YARN-5345 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > > - Improve the border/font/color etc in existing donut charts > -- Solid lines and colors might give a better looks > -- Ensure the text is confined to the empty space in the donut > -- Use color codes that convey the meaning of statuses -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-5346) [YARN-3368] Queues page improvementS
[ https://issues.apache.org/jira/browse/YARN-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-5346: - Assignee: Sreenath Somarajapuram Summary: [YARN-3368] Queues page improvementS (was: [YARN-3368] Queues page improvement) > [YARN-3368] Queues page improvementS > > > Key: YARN-5346 > URL: https://issues.apache.org/jira/browse/YARN-5346 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > > Queues page: > - Reorder contents in existing Queues page, and Improve UI components > - On clicking a queue, the user must be taken to the respective queue's > details page. > - Display queue details on mouseover > - The bar and doughnut charts doesn't update on queue change, that needs to > be fixed > Queue details page: > - Add a sub-page for all applications running under the queue -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5348) [YARN-3368] Node details page improvements
Sreenath Somarajapuram created YARN-5348: Summary: [YARN-3368] Node details page improvements Key: YARN-5348 URL: https://issues.apache.org/jira/browse/YARN-5348 Project: Hadoop YARN Issue Type: Sub-task Reporter: Sreenath Somarajapuram - Improve the component styling - Correct padding in Node Information table -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5347) [YARN-3368] Applications page improvement
Sreenath Somarajapuram created YARN-5347: Summary: [YARN-3368] Applications page improvement Key: YARN-5347 URL: https://issues.apache.org/jira/browse/YARN-5347 Project: Hadoop YARN Issue Type: Sub-task Reporter: Sreenath Somarajapuram Applications page: - Add a "Long running service" sub-page Application details page: - Improve the layout -- Correct the component borders - Remove double border & the extra space -- Layout "Application Basic Information" vertically - List attempts under the application as a subpage - Hide the diagnostics panel when, diagnostics data is not available -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5346) [YARN-3368] Queues page improvement
Sreenath Somarajapuram created YARN-5346: Summary: [YARN-3368] Queues page improvement Key: YARN-5346 URL: https://issues.apache.org/jira/browse/YARN-5346 Project: Hadoop YARN Issue Type: Sub-task Reporter: Sreenath Somarajapuram Queues page: - Reorder contents in existing Queues page, and Improve UI components - On clicking a queue, the user must be taken to the respective queue's details page. - Display queue details on mouseover - The bar and doughnut charts doesn't update on queue change, that needs to be fixed Queue details page: - Add a sub-page for all applications running under the queue -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5345) [YARN-3368] Cluster overview page improvements
Sreenath Somarajapuram created YARN-5345: Summary: [YARN-3368] Cluster overview page improvements Key: YARN-5345 URL: https://issues.apache.org/jira/browse/YARN-5345 Project: Hadoop YARN Issue Type: Sub-task Reporter: Sreenath Somarajapuram - Improve the border/font/color etc in existing donut charts -- Solid lines and colors might give a better looks -- Ensure the text is confined to the empty space in the donut -- Use color codes that convey the meaning of statuses -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5344) [YARN-3368] Generic UI improvements
Sreenath Somarajapuram created YARN-5344: Summary: [YARN-3368] Generic UI improvements Key: YARN-5344 URL: https://issues.apache.org/jira/browse/YARN-5344 Project: Hadoop YARN Issue Type: Sub-task Reporter: Sreenath Somarajapuram - Add breadcrumps in all pages - Define a vertical space (to the left) for displaying sub-pages -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5161) [YARN-3368] Add Apache Hadoop logo to UI home page
[ https://issues.apache.org/jira/browse/YARN-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369108#comment-15369108 ] Sreenath Somarajapuram commented on YARN-5161: -- +1 Looks good to me. > [YARN-3368] Add Apache Hadoop logo to UI home page > -- > > Key: YARN-5161 > URL: https://issues.apache.org/jira/browse/YARN-5161 > Project: Hadoop YARN > Issue Type: Sub-task > Components: webapp >Reporter: Sunil G >Assignee: Kai Sasaki > Attachments: Screen Shot 2016-05-31 at 21.22.30.png, Screen Shot > 2016-06-11 at 12.33.39.png, Screen Shot 2016-06-20 at 23.15.05.png, > YARN-5161-YARN-3368.03.patch, YARN-5161-YARN-3368.04.patch, > YARN-5161-YARN-3368.05.patch, YARN-5161.01.patch, YARN-5161.02.patch, > apache_logo.png, hadoop_logo.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Created] (YARN-5273) [YARN-3368] Introduce footer in YARN UI
Sreenath Somarajapuram created YARN-5273: Summary: [YARN-3368] Introduce footer in YARN UI Key: YARN-5273 URL: https://issues.apache.org/jira/browse/YARN-5273 Project: Hadoop YARN Issue Type: Sub-task Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram It would look good to have a footer in the UI that can display various basic details about the UI - To start with, display the Apache License version message with a link to the License doc. - The footer must always stick to the bottom of the page. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5161) [YARN-3368] Add Apache Hadoop logo to UI home page
[ https://issues.apache.org/jira/browse/YARN-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325735#comment-15325735 ] Sreenath Somarajapuram commented on YARN-5161: -- The texts are a bit on the lighter side. Would be better to use a more darker shade. > [YARN-3368] Add Apache Hadoop logo to UI home page > -- > > Key: YARN-5161 > URL: https://issues.apache.org/jira/browse/YARN-5161 > Project: Hadoop YARN > Issue Type: Sub-task > Components: webapp >Reporter: Sunil G >Assignee: Kai Sasaki > Attachments: Screen Shot 2016-05-31 at 21.22.30.png, Screen Shot > 2016-06-11 at 12.33.39.png, YARN-5161-YARN-3368.03.patch, > YARN-5161-YARN-3368.04.patch, YARN-5161.01.patch, YARN-5161.02.patch, > apache_logo.png, hadoop_logo.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-4097) Create POC timeline web UI with new YARN web UI framework
[ https://issues.apache.org/jira/browse/YARN-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283915#comment-15283915 ] Sreenath Somarajapuram commented on YARN-4097: -- [~gtCarrera9] I would like to help on the Ember side. Please guide me to the code where you are facing issue with ember data. > Create POC timeline web UI with new YARN web UI framework > - > > Key: YARN-4097 > URL: https://issues.apache.org/jira/browse/YARN-4097 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver >Reporter: Li Lu >Assignee: Li Lu > Attachments: Screen Shot 2016-02-24 at 15.57.38.png, Screen Shot > 2016-02-24 at 15.57.53.png, Screen Shot 2016-02-24 at 15.58.08.png, Screen > Shot 2016-02-24 at 15.58.26.png > > > As planned, we need to try out the new YARN web UI framework and implement > timeline v2 web UI on top of it. This JIRA proposes to build the basic active > flow and application lists of the timeline data. We can add more content > after we get used to this framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-3698) Correct node-manager redirection & make task attempt log files downloadable from all browsers
[
https://issues.apache.org/jira/browse/YARN-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreenath Somarajapuram updated YARN-3698:
-
Description:
Issue with redirection:
On hitting
{code}http://address:8042/node/containerlogs/container_e13_1448429572030_8751_01_000588/uname/syslog_attempt_1448429572030_8751_6_02_00_0{code}
We are getting redirected to the container logs at
{code}http://address:19888/jobhistory/logs/address:45454/container_e13_1448429572030_8751_01_000588/container_e13_1448429572030_8751_01_000588/uname{code}
The ideal behaviour must be to get the respective attempt log.
Make logs downloadable:
Please provide a variant of the link with the following headers set, this
enables direct download of the file across all browsers. Without these we
cannot provide a cross-browser download links.
Content-Disposition: attachment; filename="attempt-id.log"
Content-Type of text/plain
was:
Issue with redirection:
On hitting
{code}http://address:8042/node/containerlogs/container_e13_1448429572030_8751_01_000588/uname/syslog_attempt_1448429572030_8751_6_02_00_0{code}
We are getting redirected to the container logs at
{code}http://address:19888/jobhistory/logs/address:45454/container_e13_1448429572030_8751_01_000588/container_e13_1448429572030_8751_01_000588/uname{code}
The ideal behaviour must be to get the respective attempt log.
Provide a downloadable link:
Please provide a variant of the link with the following headers set, this
enables direct download of the file across all browsers. Without these we
cannot provide a cross-browser download links.
Content-Disposition: attachment; filename="attempt-id.log"
Content-Type of text/plain
> Correct node-manager redirection & make task attempt log files downloadable
> from all browsers
> -
>
> Key: YARN-3698
> URL: https://issues.apache.org/jira/browse/YARN-3698
> Project: Hadoop YARN
> Issue Type: Task
>Reporter: Sreenath Somarajapuram
>
> Issue with redirection:
> On hitting
> {code}http://address:8042/node/containerlogs/container_e13_1448429572030_8751_01_000588/uname/syslog_attempt_1448429572030_8751_6_02_00_0{code}
> We are getting redirected to the container logs at
> {code}http://address:19888/jobhistory/logs/address:45454/container_e13_1448429572030_8751_01_000588/container_e13_1448429572030_8751_01_000588/uname{code}
> The ideal behaviour must be to get the respective attempt log.
> Make logs downloadable:
> Please provide a variant of the link with the following headers set, this
> enables direct download of the file across all browsers. Without these we
> cannot provide a cross-browser download links.
> Content-Disposition: attachment; filename="attempt-id.log"
> Content-Type of text/plain
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3698) Correct node-manager redirection & make task attempt log files downloadable from all browsers
[
https://issues.apache.org/jira/browse/YARN-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreenath Somarajapuram updated YARN-3698:
-
Description:
Issue with redirection:
On hitting
{code}http://address:8042/node/containerlogs/container_e13_1448429572030_8751_01_000588/uname/syslog_attempt_1448429572030_8751_6_02_00_0{code}
We are getting redirected to the container logs at
{code}http://address:19888/jobhistory/logs/address:45454/container_e13_1448429572030_8751_01_000588/container_e13_1448429572030_8751_01_000588/uname{code}
The ideal behaviour must be to get the respective attempt log.
Make logs downloadable:
Please provide a variant of the link with the following headers set, this
enables direct download of the file across all browsers. Without these we
cannot provide a cross-browser download links.
{code}
Content-Disposition: attachment; filename="attempt-id.log"
Content-Type of text/plain
{code}
was:
Issue with redirection:
On hitting
{code}http://address:8042/node/containerlogs/container_e13_1448429572030_8751_01_000588/uname/syslog_attempt_1448429572030_8751_6_02_00_0{code}
We are getting redirected to the container logs at
{code}http://address:19888/jobhistory/logs/address:45454/container_e13_1448429572030_8751_01_000588/container_e13_1448429572030_8751_01_000588/uname{code}
The ideal behaviour must be to get the respective attempt log.
Make logs downloadable:
Please provide a variant of the link with the following headers set, this
enables direct download of the file across all browsers. Without these we
cannot provide a cross-browser download links.
Content-Disposition: attachment; filename="attempt-id.log"
Content-Type of text/plain
> Correct node-manager redirection & make task attempt log files downloadable
> from all browsers
> -
>
> Key: YARN-3698
> URL: https://issues.apache.org/jira/browse/YARN-3698
> Project: Hadoop YARN
> Issue Type: Task
>Reporter: Sreenath Somarajapuram
>
> Issue with redirection:
> On hitting
> {code}http://address:8042/node/containerlogs/container_e13_1448429572030_8751_01_000588/uname/syslog_attempt_1448429572030_8751_6_02_00_0{code}
> We are getting redirected to the container logs at
> {code}http://address:19888/jobhistory/logs/address:45454/container_e13_1448429572030_8751_01_000588/container_e13_1448429572030_8751_01_000588/uname{code}
> The ideal behaviour must be to get the respective attempt log.
> Make logs downloadable:
> Please provide a variant of the link with the following headers set, this
> enables direct download of the file across all browsers. Without these we
> cannot provide a cross-browser download links.
> {code}
> Content-Disposition: attachment; filename="attempt-id.log"
> Content-Type of text/plain
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3698) Correct node-manager redirection & make task attempt log files downloadable from all browsers
[
https://issues.apache.org/jira/browse/YARN-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreenath Somarajapuram updated YARN-3698:
-
Description:
Issue with redirection:
On hitting
{code}http://address:8042/node/containerlogs/container_e13_1448429572030_8751_01_000588/uname/syslog_attempt_1448429572030_8751_6_02_00_0{code}
We are getting redirected to the container logs at
{code}http://address:19888/jobhistory/logs/address:45454/container_e13_1448429572030_8751_01_000588/container_e13_1448429572030_8751_01_000588/uname{code}
The ideal behaviour must be to get the respective attempt log.
Provide a downloadable link:
Please provide a variant of the link with the following headers set, this
enables direct download of the file across all browsers. Without these we
cannot provide a cross-browser download links.
Content-Disposition: attachment; filename="attempt-id.log"
Content-Type of text/plain
was:
Currently we don't have direct access to an attempt's log file from web apps.
The only available option is through jobhistory, and that provides an HTML view
of the log.
Would be great if we provide raw log files for the users to download.
Requirements:
# A link to access the raw log file.
# A variant of the link with the following headers set, this enables direct
download of the file across all browsers. Without these we cannot provide a
cross-browser download link.
Content-Disposition: attachment; filename="attempt-id.log"
Content-Type of text/plain
# Correct nodemanager redirection:
-- Node manager redirects an attempt syslog view to the container view. Hence
we are not able to view the logs of a specific attempt.
-- Before redirection:
http://sandbox.hortonworks.com:8042/node/containerlogs/container_1432048982252_0004_01_02/root/syslog_attempt_1432048982252_0004_1_02_00_0
-- After redirection:
http://sandbox.hortonworks.com:19888/jobhistory/logs/sandbox.hortonworks.com:45454/container_1432048982252_0004_01_02/container_1432048982252_0004_01_02/root
> Correct node-manager redirection & make task attempt log files downloadable
> from all browsers
> -
>
> Key: YARN-3698
> URL: https://issues.apache.org/jira/browse/YARN-3698
> Project: Hadoop YARN
> Issue Type: Task
>Reporter: Sreenath Somarajapuram
>
> Issue with redirection:
> On hitting
> {code}http://address:8042/node/containerlogs/container_e13_1448429572030_8751_01_000588/uname/syslog_attempt_1448429572030_8751_6_02_00_0{code}
> We are getting redirected to the container logs at
> {code}http://address:19888/jobhistory/logs/address:45454/container_e13_1448429572030_8751_01_000588/container_e13_1448429572030_8751_01_000588/uname{code}
> The ideal behaviour must be to get the respective attempt log.
> Provide a downloadable link:
> Please provide a variant of the link with the following headers set, this
> enables direct download of the file across all browsers. Without these we
> cannot provide a cross-browser download links.
> Content-Disposition: attachment; filename="attempt-id.log"
> Content-Type of text/plain
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (YARN-3698) Make task attempt log files accessible from webapps & correct node-manager redirection
[ https://issues.apache.org/jira/browse/YARN-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-3698: - Description: Currently we don't have direct access to an attempt's log file from web apps. The only available option is through jobhistory, and that provides an HTML view of the log. Would be great if we provide raw log files for the users to download. Requirements: # A link to access the raw log file. # A variant of the link with the following headers set, this enables direct download of the file across all browsers. Without these we cannot provide a cross-browser download link. Content-Disposition: attachment; filename="attempt-id.log" Content-Type of text/plain # Correct redirection: - Node manager redirects an attempt syslog view to the container view. Hence we are not able to view the logs of a specific attempt. Before redirection: http://sandbox.hortonworks.com:8042/node/containerlogs/container_1432048982252_0004_01_02/root/syslog_attempt_1432048982252_0004_1_02_00_0 After redirection: http://sandbox.hortonworks.com:19888/jobhistory/logs/sandbox.hortonworks.com:45454/container_1432048982252_0004_01_02/container_1432048982252_0004_01_02/root was: Currently we don't have direct access to an attempt's log file from web apps. The only available option is through jobhistory, and that provides an HTML view of the log. Requirements: # A link to access the raw log file. # A variant of the link with the following headers set, this enables direct download of the file across all browsers. Content-Disposition: attachment; filename="attempt-id.log" Content-Type of text/plain # Node manager redirects an attempt syslog view to the container view. Hence we are not able to view the logs of a specific attempt. Before redirection: http://sandbox.hortonworks.com:8042/node/containerlogs/container_1432048982252_0004_01_02/root/syslog_attempt_1432048982252_0004_1_02_00_0 After redirection: http://sandbox.hortonworks.com:19888/jobhistory/logs/sandbox.hortonworks.com:45454/container_1432048982252_0004_01_02/container_1432048982252_0004_01_02/root > Make task attempt log files accessible from webapps & correct node-manager > redirection > -- > > Key: YARN-3698 > URL: https://issues.apache.org/jira/browse/YARN-3698 > Project: Hadoop YARN > Issue Type: Task >Reporter: Sreenath Somarajapuram > > Currently we don't have direct access to an attempt's log file from web apps. > The only available option is through jobhistory, and that provides an HTML > view of the log. > Would be great if we provide raw log files for the users to download. > Requirements: > # A link to access the raw log file. > # A variant of the link with the following headers set, this enables direct > download of the file across all browsers. Without these we cannot provide a > cross-browser download link. > Content-Disposition: attachment; filename="attempt-id.log" > Content-Type of text/plain > # Correct redirection: > - Node manager redirects an attempt syslog view to the container view. Hence > we are not able to view the logs of a specific attempt. > Before redirection: > http://sandbox.hortonworks.com:8042/node/containerlogs/container_1432048982252_0004_01_02/root/syslog_attempt_1432048982252_0004_1_02_00_0 > After redirection: > http://sandbox.hortonworks.com:19888/jobhistory/logs/sandbox.hortonworks.com:45454/container_1432048982252_0004_01_02/container_1432048982252_0004_01_02/root -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-3698) Make task attempt log files accessible from webapps & correct node-manager redirection
[ https://issues.apache.org/jira/browse/YARN-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-3698: - Description: Currently we don't have direct access to an attempt's log file from web apps. The only available option is through jobhistory, and that provides an HTML view of the log. Would be great if we provide raw log files for the users to download. Requirements: # A link to access the raw log file. # A variant of the link with the following headers set, this enables direct download of the file across all browsers. Without these we cannot provide a cross-browser download link. Content-Disposition: attachment; filename="attempt-id.log" Content-Type of text/plain # Correct nodemanager redirection: -- Node manager redirects an attempt syslog view to the container view. Hence we are not able to view the logs of a specific attempt. -- Before redirection: http://sandbox.hortonworks.com:8042/node/containerlogs/container_1432048982252_0004_01_02/root/syslog_attempt_1432048982252_0004_1_02_00_0 -- After redirection: http://sandbox.hortonworks.com:19888/jobhistory/logs/sandbox.hortonworks.com:45454/container_1432048982252_0004_01_02/container_1432048982252_0004_01_02/root was: Currently we don't have direct access to an attempt's log file from web apps. The only available option is through jobhistory, and that provides an HTML view of the log. Would be great if we provide raw log files for the users to download. Requirements: # A link to access the raw log file. # A variant of the link with the following headers set, this enables direct download of the file across all browsers. Without these we cannot provide a cross-browser download link. Content-Disposition: attachment; filename="attempt-id.log" Content-Type of text/plain # Correct redirection: - Node manager redirects an attempt syslog view to the container view. Hence we are not able to view the logs of a specific attempt. Before redirection: http://sandbox.hortonworks.com:8042/node/containerlogs/container_1432048982252_0004_01_02/root/syslog_attempt_1432048982252_0004_1_02_00_0 After redirection: http://sandbox.hortonworks.com:19888/jobhistory/logs/sandbox.hortonworks.com:45454/container_1432048982252_0004_01_02/container_1432048982252_0004_01_02/root > Make task attempt log files accessible from webapps & correct node-manager > redirection > -- > > Key: YARN-3698 > URL: https://issues.apache.org/jira/browse/YARN-3698 > Project: Hadoop YARN > Issue Type: Task >Reporter: Sreenath Somarajapuram > > Currently we don't have direct access to an attempt's log file from web apps. > The only available option is through jobhistory, and that provides an HTML > view of the log. > Would be great if we provide raw log files for the users to download. > Requirements: > # A link to access the raw log file. > # A variant of the link with the following headers set, this enables direct > download of the file across all browsers. Without these we cannot provide a > cross-browser download link. > Content-Disposition: attachment; filename="attempt-id.log" > Content-Type of text/plain > # Correct nodemanager redirection: > -- Node manager redirects an attempt syslog view to the container view. Hence > we are not able to view the logs of a specific attempt. > -- Before redirection: > http://sandbox.hortonworks.com:8042/node/containerlogs/container_1432048982252_0004_01_02/root/syslog_attempt_1432048982252_0004_1_02_00_0 > -- After redirection: > http://sandbox.hortonworks.com:19888/jobhistory/logs/sandbox.hortonworks.com:45454/container_1432048982252_0004_01_02/container_1432048982252_0004_01_02/root -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4238) createdTime and modifiedTime is not reported while publishing entities to ATSv2
[ https://issues.apache.org/jira/browse/YARN-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15087527#comment-15087527 ] Sreenath Somarajapuram commented on YARN-4238: -- Thanks [~varun_saxena] Also is it possible to query records in ascending & descending order of creation? > createdTime and modifiedTime is not reported while publishing entities to > ATSv2 > --- > > Key: YARN-4238 > URL: https://issues.apache.org/jira/browse/YARN-4238 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver >Affects Versions: YARN-2928 >Reporter: Varun Saxena >Assignee: Varun Saxena > Labels: yarn-2928-1st-milestone > Attachments: YARN-4238-YARN-2928.01.patch, > YARN-4238-feature-YARN-2928.002.patch, YARN-4238-feature-YARN-2928.003.patch, > YARN-4238-feature-YARN-2928.02.patch > > > While publishing entities from RM and elsewhere we are not sending created > time. For instance, created time in TimelineServiceV2Publisher class and for > other entities in other such similar classes is not updated. We can easily > update created time when sending application created event. Likewise for > modification time on every write. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4238) createdTime and modifiedTime is not reported while publishing entities to ATSv2
[ https://issues.apache.org/jira/browse/YARN-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15086967#comment-15086967 ] Sreenath Somarajapuram commented on YARN-4238: -- Hi, Tez UI doesn't use modified time while querying. But that said, I was wondering what might be the order in which we get back records. For instance if I ask for 10 records. - Would they be returned in the order of creation ? or - Would they be returned in the order of modification? or - Would it be just random? > createdTime and modifiedTime is not reported while publishing entities to > ATSv2 > --- > > Key: YARN-4238 > URL: https://issues.apache.org/jira/browse/YARN-4238 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver >Affects Versions: YARN-2928 >Reporter: Varun Saxena >Assignee: Varun Saxena > Labels: yarn-2928-1st-milestone > Attachments: YARN-4238-YARN-2928.01.patch, > YARN-4238-feature-YARN-2928.002.patch, YARN-4238-feature-YARN-2928.003.patch, > YARN-4238-feature-YARN-2928.02.patch > > > While publishing entities from RM and elsewhere we are not sending created > time. For instance, created time in TimelineServiceV2Publisher class and for > other entities in other such similar classes is not updated. We can easily > update created time when sending application created event. Likewise for > modification time on every write. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4516) [YARN-3368] Use em-table to better render tables
[ https://issues.apache.org/jira/browse/YARN-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15075107#comment-15075107 ] Sreenath Somarajapuram commented on YARN-4516: -- You can pass any ember array as rows to the table. Please share a patch to get a better idea about the current implementation. Will add a sample to the dummy app soon. > [YARN-3368] Use em-table to better render tables > > > Key: YARN-4516 > URL: https://issues.apache.org/jira/browse/YARN-4516 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Li Lu > > Currently we're using DataTables, it isn't integrated to Ember.js very well. > Instead we can use em-table (see https://github.com/sreenaths/em-table/wiki, > which is created for Tez UI). It supports features such as selectable > columns, pagination, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4516) [YARN-3368] Use em-table to better render tables
[ https://issues.apache.org/jira/browse/YARN-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073630#comment-15073630 ] Sreenath Somarajapuram commented on YARN-4516: -- [~gtCarrera9] I have added ColumnDefinition.makeFromModel function in the latest version. Given a model it would give you column definitions. Please find a sample implementation in the dummy app. Hope this helps. > [YARN-3368] Use em-table to better render tables > > > Key: YARN-4516 > URL: https://issues.apache.org/jira/browse/YARN-4516 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Li Lu > > Currently we're using DataTables, it isn't integrated to Ember.js very well. > Instead we can use em-table (see https://github.com/sreenaths/em-table/wiki, > which is created for Tez UI). It supports features such as selectable > columns, pagination, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4516) [YARN-3368] Use em-table to better render tables
[ https://issues.apache.org/jira/browse/YARN-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073493#comment-15073493 ] Sreenath Somarajapuram commented on YARN-4516: -- Thanks [~gtCarrera9] That sounds like a good idea, its not supported yet. Adding it into the roadmap. > [YARN-3368] Use em-table to better render tables > > > Key: YARN-4516 > URL: https://issues.apache.org/jira/browse/YARN-4516 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan >Assignee: Li Lu > > Currently we're using DataTables, it isn't integrated to Ember.js very well. > Instead we can use em-table (see https://github.com/sreenaths/em-table/wiki, > which is created for Tez UI). It supports features such as selectable > columns, pagination, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (YARN-4516) [YARN-3368] Use em-table to better render tables
[ https://issues.apache.org/jira/browse/YARN-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072526#comment-15072526 ] Sreenath Somarajapuram commented on YARN-4516: -- [~gtCarrera9] Feel free to take-up the task after checking with [~leftnoteasy]. Please let me know if you need any help with em-table. > [YARN-3368] Use em-table to better render tables > > > Key: YARN-4516 > URL: https://issues.apache.org/jira/browse/YARN-4516 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Wangda Tan > > Currently we're using DataTables, it isn't integrated to Ember.js very well. > Instead we can use em-table (see https://github.com/sreenaths/em-table/wiki, > which is created for Tez UI). It supports features such as selectable > columns, pagination, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-3698) Make task attempt log files accessible from webapps
[ https://issues.apache.org/jira/browse/YARN-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-3698: - Description: Currently we don't have direct access to an attempt's log file from web apps. The only available option is through jobhistory, and that provides an HTML view of the log. Requirements: # A link to access the raw log file. # A variant of the link with the following headers set, this enables direct download of the file across all browsers. Content-Disposition: attachment; filename=attempt-id.log Content-Type of text/plain # Node manager redirects an attempt syslog view to the container view. Hence we are not able to view the logs of a specific attempt. Before redirection: http://sandbox.hortonworks.com:8042/node/containerlogs/container_1432048982252_0004_01_02/root/syslog_attempt_1432048982252_0004_1_02_00_0 After redirection: http://sandbox.hortonworks.com:19888/jobhistory/logs/sandbox.hortonworks.com:45454/container_1432048982252_0004_01_02/container_1432048982252_0004_01_02/root was: Currently we don't have direct access to an attempt's log file from web apps. The only available option is through jobhistory, and that provides an HTML view of the log. Requirements: # A link to access the raw log file. # A variant of the link with the following headers set, this enables direct download of the file across all browsers. Content-Disposition: attachment; filename=attempt-id.log Content-Type of text/plain Make task attempt log files accessible from webapps --- Key: YARN-3698 URL: https://issues.apache.org/jira/browse/YARN-3698 Project: Hadoop YARN Issue Type: Task Reporter: Sreenath Somarajapuram Currently we don't have direct access to an attempt's log file from web apps. The only available option is through jobhistory, and that provides an HTML view of the log. Requirements: # A link to access the raw log file. # A variant of the link with the following headers set, this enables direct download of the file across all browsers. Content-Disposition: attachment; filename=attempt-id.log Content-Type of text/plain # Node manager redirects an attempt syslog view to the container view. Hence we are not able to view the logs of a specific attempt. Before redirection: http://sandbox.hortonworks.com:8042/node/containerlogs/container_1432048982252_0004_01_02/root/syslog_attempt_1432048982252_0004_1_02_00_0 After redirection: http://sandbox.hortonworks.com:19888/jobhistory/logs/sandbox.hortonworks.com:45454/container_1432048982252_0004_01_02/container_1432048982252_0004_01_02/root -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-3698) Make task attempt log files accessible from webapps correct node-manager redirection
[ https://issues.apache.org/jira/browse/YARN-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated YARN-3698: - Summary: Make task attempt log files accessible from webapps correct node-manager redirection (was: Make task attempt log files accessible from webapps) Make task attempt log files accessible from webapps correct node-manager redirection -- Key: YARN-3698 URL: https://issues.apache.org/jira/browse/YARN-3698 Project: Hadoop YARN Issue Type: Task Reporter: Sreenath Somarajapuram Currently we don't have direct access to an attempt's log file from web apps. The only available option is through jobhistory, and that provides an HTML view of the log. Requirements: # A link to access the raw log file. # A variant of the link with the following headers set, this enables direct download of the file across all browsers. Content-Disposition: attachment; filename=attempt-id.log Content-Type of text/plain # Node manager redirects an attempt syslog view to the container view. Hence we are not able to view the logs of a specific attempt. Before redirection: http://sandbox.hortonworks.com:8042/node/containerlogs/container_1432048982252_0004_01_02/root/syslog_attempt_1432048982252_0004_1_02_00_0 After redirection: http://sandbox.hortonworks.com:19888/jobhistory/logs/sandbox.hortonworks.com:45454/container_1432048982252_0004_01_02/container_1432048982252_0004_01_02/root -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3698) Make task attempt log files accessible from webapps
Sreenath Somarajapuram created YARN-3698: Summary: Make task attempt log files accessible from webapps Key: YARN-3698 URL: https://issues.apache.org/jira/browse/YARN-3698 Project: Hadoop YARN Issue Type: Task Reporter: Sreenath Somarajapuram Currently we don't have direct access to an attempt's log file from web apps. The only available option is through jobhistory, and that provides an HTML view of the log. Requirements: # A link to access the raw log file. # A variant of the link with the following headers set, this enables direct download of the file across all browsers. Content-Disposition: attachment; filename=attempt-id.log Content-Type of text/plain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
