[jira] [Commented] (YARN-2238) filtering on UI sticks even if I move away from the page
[ https://issues.apache.org/jira/browse/YARN-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14058176#comment-14058176 ] Garth Goodson commented on YARN-2238: - We have the same issue and it is very annoying for our users. If the front page is being filtered, it should be able to be cleared from that page. filtering on UI sticks even if I move away from the page Key: YARN-2238 URL: https://issues.apache.org/jira/browse/YARN-2238 Project: Hadoop YARN Issue Type: Bug Components: webapp Affects Versions: 2.4.0 Reporter: Sangjin Lee Attachments: filtered.png The main data table in many web pages (RM, AM, etc.) seems to show an unexpected filtering behavior. If I filter the table by typing something in the key or value field (or I suspect any search field), the data table gets filtered. The example I used is the job configuration page for a MR job. That is expected. However, when I move away from that page and visit any other web page of the same type (e.g. a job configuration page), the page is rendered with the filtering! That is unexpected. What's even stranger is that it does not render the filtering term. As a result, I have a page that's mysteriously filtered but doesn't tell me what it's filtering on. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (YARN-558) Add ability to completely remove nodemanager from resourcemanager.
Garth Goodson created YARN-558: -- Summary: Add ability to completely remove nodemanager from resourcemanager. Key: YARN-558 URL: https://issues.apache.org/jira/browse/YARN-558 Project: Hadoop YARN Issue Type: Improvement Components: resourcemanager Reporter: Garth Goodson Priority: Minor I would like to add the ability to completely remove a nodemanager from the resourcemanager's state. I run a cloud service where I want to dynamically bring up nodes to act as nodemanagers and then bring them down again when not needed. These nodes have dynamically assigned IPs, thus the alternative of decommissioning them via an excludes file leads to a large (unbounded) list of decommissioned nodes that may never be commissioned again. I would like the ability to move a node from a decommissioned state to completely removing it from the resource manager. I have thought of two ways of implementing this. 1) Add an optional timeout between the decommission state - being removed from the nodemanager. 2) Add an explicit RPC to remove a node that is decommissioned. Any additional thoughts/discussion are welcome. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
