[
https://issues.apache.org/jira/browse/STORM-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-4051.
----------------------------------
Resolution: Fixed
> Scheduler needs to include acker memory for topology resources
> --------------------------------------------------------------
>
> Key: STORM-4051
> URL: https://issues.apache.org/jira/browse/STORM-4051
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Aaron Gresch
> Assignee: Aaron Gresch
> Priority: Major
> Fix For: 2.6.3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
