[MESOS-10097] After HTTP framework disconnects, heartbeater idle-loops instead of being deleted.

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5.3, 1.6.2, 1.7.2, 1.8.1, 1.9.0
• Fix Version/s: 1.10.0
• Component/s: master
• Target Version/s: 1.10.0
• Story Points: 1
• Assignee: Andrei Sekretenko
• Reporter: Andrei Sekretenko
• Created: 13/Feb/20 11:19
• Updated: 19/Mar/20 22:35
• Resolved: 14/Feb/20 16:24

Description

In some cases, Master closes connection of HTTP framework without deleting the heartbeater:
https://github.com/apache/mesos/blob/65e18bef2c5ff356ef74bac9aa79b128c5b186d9/src/master/master.cpp#L3323
https://github.com/apache/mesos/blob/65e18bef2c5ff356ef74bac9aa79b128c5b186d9/src/master/master.cpp#L10910

It can be argued that this does not constitute a leak, because old heartbeaters are deleted on reconnection/removal.

However, this means that for each disconnected framework there is a ResponseHeartbeaterProcess that performs an idle loop.

Issue Links

• is related to: MESOS-10056 Perform synchronous authorization for scheduler calls.