[
https://issues.apache.org/jira/browse/YUNIKORN-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190631#comment-17190631
]
Weihao Zheng edited comment on YUNIKORN-387 at 9/4/20, 8:48 AM:
----------------------------------------------------------------
Thanks [~wwei] and [~wilfreds] for your comments and ideas. I have updated the
design doc. We simplify the design of scheduler tracing, delete the REST API
for fetching scheduler traces and move the tracer to the core. Sampling and
on-demand tracing should be an important part of the design. I list our current
design about it in implementation notes and look forward to your advice.
Hope to hear your thoughts.
was (Author: weihao zheng):
Thanks [~wwei] and [~wilfreds] for your comments and ideas. I have updated the
design doc. We simplify the design of scheduler tracing, delete the REST API
for fetching scheduler traces and move the tracer to the core. Sampling and
on-demand tracing should be an important part of the design. I list our current
thought about it in implementation notes and look forward to your advice.
Hope to hear your thoughts.
> Use Tracing to Improve YuniKorn's Observability
> -----------------------------------------------
>
> Key: YUNIKORN-387
> URL: https://issues.apache.org/jira/browse/YUNIKORN-387
> Project: Apache YuniKorn
> Issue Type: New Feature
> Components: core - scheduler, shim - kubernetes
> Reporter: Weihao Zheng
> Priority: Major
>
> We can use existing tracing framework to collect tracing information in a
> standardized format for scheduling and resource management. It will improve
> YuniKorn's observability significantly with less work. Here are our design
> ideas:
> [https://docs.google.com/document/d/1MKL9SfTH8Pjw6kBM0vRnyv_ctnxBHAz-iuA7Zbux60E/edit?usp=sharing]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
