-
Notifications
You must be signed in to change notification settings - Fork 161
feat(BA-1443): backend.ai mgr scheduler last-execution-time
command
#4507
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@click.argument("scheduler_name", required=False) | ||
@click.pass_obj | ||
def last_execution_time( | ||
cli_ctx: CLIContext, | ||
scheduler_name: str | None, | ||
*, | ||
format: Literal["plain"] | Literal["csv"] | Literal["json"] = "plain", | ||
manager_id: str | None = None, | ||
) -> None: | ||
"""Queries manager's scheduler execution footprint from Redis. When scheduler name is not specified, this command will return informations of all schedulers in store.""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like last_execution_time returns more information than the name.
Would footprint be a better name?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"footprint" looks good, perhaps we can count more generic term like "information".
resolves #4506 (BA-1443). This PR adds new command set to manager CLI implementation (not
client-py
).The command accepts
scheduler_name
, which refers target scheduler name to look up, and--manager-id, which defines which manager node to fetch information of, being set as the local manager executing the command by default. When not specifying
scheduler_name` argument, the command will return status of every schedulers operated from the target manager node. On a complicated cluster with multiple active Backend.AI managers operating concurrently, Backend.AI keeps track of each manager node's last execution time of each scheduler locally, not on a global redis key namespace, hence requiring CLI users to fetch status of each manager individually.Checklist: (if applicable)