[ https://issues.apache.org/jira/browse/TWILL-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954214#comment-15954214 ]
ASF GitHub Bot commented on TWILL-176: -------------------------------------- GitHub user chtyim opened a pull request: https://github.com/apache/twill/pull/52 (TWILL-176) Redirect all requests to tracker URL to /resources path - "/resources" is the only path supported for the tracker service for now You can merge this pull request into a Git repository by running: $ git pull https://github.com/chtyim/twill feature/TWILL-176 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/twill/pull/52.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #52 ---- commit b07fd47e3e78ad80097e26a944baceebefd0559c Author: Terence Yim <cht...@apache.org> Date: 2017-04-03T21:42:44Z (TWILL-176) Redirect all requests to tracker URL to /resources path - "/resources" is the only path supported for the tracker service for now ---- > Set ResourceManager tracking URL to resources path. > --------------------------------------------------- > > Key: TWILL-176 > URL: https://issues.apache.org/jira/browse/TWILL-176 > Project: Apache Twill > Issue Type: Bug > Components: yarn > Reporter: Albert Shau > > The resource manager tracking url is currently set to the host and port only. > There is nothing exposing the fact that you can append 'resources' to the > path to get a list of containers and information about each container. > This was done because the YARN api was to working properly at the time, but > we should re-investigate to see if this is still the case, or perhaps serve > some base page there that links to the resources page, plus anything else we > decide to add in the future. -- This message was sent by Atlassian JIRA (v6.3.15#6346)