[
https://issues.apache.org/jira/browse/YUNIKORN-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078962#comment-17078962
]
Weiwei Yang commented on YUNIKORN-75:
-------------------------------------
Hmm, it looks like all are a big amount of work.
Briefly chatted with [~wilfreds] on these options, but none of them seem to fit
very well. I think there is another option: we can create a common pkg in
scheduler-interface repo, and move the logging library to scheduler-interface.
Then both shim and core can simply re-use that lib. The structure
lib/go/pkg/common, (lib/java/org/apache/...). This helps us:
# clean up a lot of dup code, such as common code for logging, utility,
resource
# benefit future if we want to add more common data structure
But I have to admit this is a lot of work, let's work on other higher priority
things first. Keep the discussion going. Once reach a consensus solution, we
can revisit this in the next release.
> REST API for changing log level
> -------------------------------
>
> Key: YUNIKORN-75
> URL: https://issues.apache.org/jira/browse/YUNIKORN-75
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - scheduler
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need a rest API to change the logging level, so we can change the logging
> level on-the-fly. It can be used to debug in production issues where for most
> of the time, only INFO level log is needed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
