Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Node is still attempted to be used after removal #128

Open
blokhin opened this issue Feb 20, 2024 · 0 comments
Open

Node is still attempted to be used after removal #128

blokhin opened this issue Feb 20, 2024 · 0 comments
Labels
invalid This doesn't seem right

Comments

@blokhin
Copy link
Member

blokhin commented Feb 20, 2024 •
edited
Loading

Basically

$ yasetnode 65.108.159.113 --remove-hard

that succeeds, and after about an hour:

INFO:yascheduler.Scheduler:THREADS: 62 NODES: busy:1/enabled:2/total:2 TASKS: run:1/todo:0/done:10
INFO:yascheduler.Scheduler:QUEUES: conn_machine: 0/0 allocate: 0/0 deallocate: 0/0 consume: 0/0
^C
INFO:yascheduler:Received signal Interrupt
INFO:yascheduler.Scheduler:Stopping...
INFO:yascheduler.Scheduler.CloudAPIManager:Stopping clouds...
INFO:yascheduler.Scheduler:Disconnecting from machines: 116.203.217.118, 65.108.159.113, 135.181.107.47
INFO:yascheduler:Cancelling 2 outstanding tasks
INFO:yascheduler:Done

65.108.159.113 is still referenced in the machines list
@blokhin blokhin added the invalid This doesn't seem right label Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
invalid This doesn't seem right
Milestone
No milestone
Development

No branches or pull requests
1 participant
@blokhin