[
https://issues.apache.org/jira/browse/YARN-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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: [email protected]
For additional commands, e-mail: [email protected]
