Azure / Azure/cyclecloud-scalelib
Node info is not synced when it's deleted
- Dominant language
- Python
- Stars
- 10
- Forks
- 16
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
https://github.com/Azure/cyclecloud-scalelib/blob/4efda02a70be0ac93cffc932e9ce5de33d90432d/src/hpc/autoscale/job/demandcalculator.py#L266
Node is deleted by self.node_mgr but it's not synced back with self.__scheduler_nodes_queue, neither self.node_history. Is it an issue? Or the `DemandCalculator.delete` method has some special use pattern? @ryanhamel
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at src/hpc/autoscale/job/demandcalculator.py#L266 and trace DemandCalculator.delete, self.node_mgr, self.__scheduler_nodes_queue, and self.node_history. Determine whether deleting a node must update both stores, then confirm the expected behavior and capture a reproducible result or agreed change; no test or entry point is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100