[STORM-4051] Scheduler needs to include acker memory for topology resources

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.3
• Assignee: Aaron Gresch
• Reporter: Aaron Gresch
• Created: 05/Apr/24 17:44
• Updated: 05/Apr/24 17:45
• Resolved: 05/Apr/24 17:45

Description

The scheduler has a bug where acker memory is not considered in the scheduling estimate. The case I found was where a topology should fit on two supervisors, but the cluster has 1 available and 2 blacklisted. The scheduler thinks the topology should fit on one supervisor and fails to schedule, but also fails to release a supervisor from the blacklist, resulting in the topology never getting scheduled.

With this fix, the scheduler properly detects the topology will need to be scheduled on two supervisors and releases one from the blacklist and schedules successfully.

Switched some scheduling logs from trace to debug to make debugging scheduling issues easier.