Skip to content
This repository has been archived by the owner on Feb 1, 2022. It is now read-only.

Rank allocation to -1 when the underlying node is not ready #101

Open
ykale opened this issue Oct 6, 2020 · 2 comments
Open

Rank allocation to -1 when the underlying node is not ready #101

ykale opened this issue Oct 6, 2020 · 2 comments

Comments

@ykale
Copy link

ykale commented Oct 6, 2020

Rank allocation to -1 when the underlying node is not ready

Typically when running the xgboost operator in autoscale mode and more nodes are required, the operator allocates a negative rank to the pods instead of waiting till some threshold time and fails. This is observed in Azure Kubernetes Service.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the labels:

Label Probability
kind/bug 0.85
area/front-end 0.77
area/operator 0.98

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

@merlintang
Copy link
Contributor

this is a good point, can you send a PR to fix this ?

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

2 participants