Skip to content
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.

The job status is confusing, especially when not all the containers are ready. #2051

Closed
hao1939 opened this issue Jan 23, 2019 · 2 comments
Closed

Comments

@hao1939
Copy link
Contributor

hao1939 commented Jan 23, 2019

As below, only the slave:2 was ready.
image

Now the job is not ready, and user may confused with the status running.
If we define the running different from user's common sense, user will confuse.

@scarlett2018
Copy link
Member

As discussed in the team meeting, one quick resolution to this problem is to add a "task status" column, so that user knows the job had started to allocate resources for tasks, and some of the tasks are still waiting for resources.

@yqwang-ms
Copy link
Member

Solved by #2135

@yqwang-ms yqwang-ms self-assigned this Feb 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants