To debug exceptions like "org.apache.flink.util.FlinkException: The assigned slot <SlotId> was removed." in the master container it is often helpful to know, which slot was provided by which Taskmanager. The only way to relate slots to TaskManagers right now, seems to be to enable DEBUG logging for `org.apache.flink.runtime.jobmaster.slotpool.SlotPool`.
This would be solved, if each Taskmanager would log out their `ResouceID` during startup as the `SlotID` mainly consists of the `ResourceID` of the providing Taskmanager. For Mesos and YARN the `ResourceID` has an intrinsic meaning, but for a stand-alone or containerized setup the `ResourceID` is just the a random ID.