You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Weiwei Yang (Jira)" <ji...@apache.org> on 2020/03/26 04:32:00 UTC
[jira] [Comment Edited] (YUNIKORN-14) Add rest API to retrieve
app/container history info
[ https://issues.apache.org/jira/browse/YUNIKORN-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067350#comment-17067350 ]
Weiwei Yang edited comment on YUNIKORN-14 at 3/26/20, 4:31 AM:
---------------------------------------------------------------
Hi [~wilfreds]
Thanks for the comments.
The history info here just provides very basic info about the cluster, e.g # of containers/apps in the last 12h. I think we can leverage this simple solution to give a basic impression for users. For comprehensive metrics, we have Prometheus integration so we can push that to its store for persistent. Here, we just need a small time-bound cache just like [~adam.antal] has implemented.
It is a pull mode, but that's fine. We are doing the pull once per minute (or maybe 30s), since the data is cached, no matter how many requests from web UI, it will not lock partition and damage scheduler performance. For the moment where write happens, it simply gets the data from partition without any calculation, the impact is trivial.
The push mode is the Prometheus metrics, which we already have so I don't think we need to build anything similar.
was (Author: wwei):
Hi [~wilfreds]
Thanks for the comments.
The history info here just provides very basic info about the cluster, e.g # of containers/apps in the last 12h. I think we can leverage this simple solution to give a basic impression for users. For comprehensive metrics, we have Prometheus integration so we can push that to its store for persistent. Here, we just need a small time-bound cache just like [~adam.antal] has implemented.
It is a pull mode, but that's fine. We are doing the pull once per minute (or maybe 30s), since the data is cached, no matter how many requests from web UI, it will not lock partition and damage scheduler performance. For the moment where write happens, it simply gets the data from partition without any calculation, the impact is trivial.
The push mode is the Prometheus metrics, which we already have so I don't think we need to build anything similar.
> Add rest API to retrieve app/container history info
> ---------------------------------------------------
>
> Key: YUNIKORN-14
> URL: https://issues.apache.org/jira/browse/YUNIKORN-14
> Project: Apache YuniKorn
> Issue Type: New Feature
> Components: core - scheduler
> Reporter: Wilfred Spiegelenburg
> Assignee: Adam Antal
> Priority: Major
> Labels: pull-request-available
> Attachments: Yunikorn_UI.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As part of the web UI we can show application and container history.
> The current pages are mocked up and do not show the real history. Before the changes can be made on the web UI side we need to provide the history via a REST interface so it can be consumed by the UI.
> All web service code is located in package [https://github.com/apache/incubator-yunikorn-core/tree/master/pkg/webservice]. When running the scheduler locally (from K8shim using "make run"), the REST APIs can be accessed via
> * [http://localhost:9080/ws/v1/apps]
> * [http://localhost:9080/ws/v1/queues]
> * [http://localhost:9080/ws/v1/nodes]
> We need to add another endpoint to provide data to yunikorn-web to render the app/container history page. Please check with [~akhilpb] for the desired data format, etc. That issue is tracked via YUNIKORN-8.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org