[
https://issues.apache.org/jira/browse/YARN-9578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857521#comment-16857521
]
Tao Yang edited comment on YARN-9578 at 6/6/19 10:43 AM:
---------------------------------------------------------
Thanks [~cheersyang] for the review.
{quote}
Since you are supporting a limit number of records here, instead of cutting off
from a full list, can it be done while generating the allocations?
{quote}
limit option is used for querying partial app activities in some scenarios that
don't need all activities to reduce cost, but for some scenarios such as need a
summary of activities, all app activities can be needed, accordingly max length
of app activities stored in cache should be decided by a global configuration
which is
"yarn.resourcemanager.activities-manager.app-activities.max-queue-length" now
or a certain ratio(for example 1.2) times number of nodes in the cluster if
beyond the configuration value and multi-node is disabled, instead of an input
parameter of REST API
{quote}
query parameter ACTIONS, it looks like this is always required. But the form is
not a very RESTful pattern
{quote}
Sometimes we need both actions( get and update) to get activities in cache
meanwhile trigger an update, and that is the default way we used before and now.
{quote}
Can we rename "UPDATE" to "REFRESH"?
{quote}
Make sense to me.
was (Author: tao yang):
Thanks [~cheersyang] for the review.
{qoute}
Since you are supporting a limit number of records here, instead of cutting off
from a full list, can it be done while generating the allocations?
{quote}
limit option is used for querying partial app activities in some scenarios that
don't need all activities to reduce cost, but for some scenarios such as need a
summary of activities, all app activities can be needed, accordingly max length
of app activities stored in cache should be decided by a global configuration
which is
"yarn.resourcemanager.activities-manager.app-activities.max-queue-length" now
or a certain ratio(for example 1.2) times number of nodes in the cluster if
beyond the configuration value and multi-node is disabled, instead of an input
parameter of REST API
{quote}
query parameter ACTIONS, it looks like this is always required. But the form is
not a very RESTful pattern
{quote}
Sometimes we need both actions( get and update) to get activities in cache
meanwhile trigger an update, and that is the default way we used before and now.
{quote}
Can we rename "UPDATE" to "REFRESH"?
{quote}
Make sense to me.
> Add limit/actions/summarize options for app activities REST API
> ---------------------------------------------------------------
>
> Key: YARN-9578
> URL: https://issues.apache.org/jira/browse/YARN-9578
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacityscheduler
> Reporter: Tao Yang
> Assignee: Tao Yang
> Priority: Major
> Attachments: YARN-9578.001.patch, YARN-9578.002.patch,
> YARN-9578.003.patch, YARN-9578.004.patch, YARN-9578.005.patch
>
>
> Currently all completed activities of specified application in cache will be
> returned for application activities REST API. Most results may be redundant
> in some scenarios which only need a few latest results, for example, perhaps
> only one result is needed to be shown on UI for debugging.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
