Github user beyond1920 commented on the issue:
https://github.com/apache/flink/pull/2571
@mxm, What would happen under following cases: taskExecutor releases a
registered slot, then taskExecutor reports its latest slotReport to
ResourceManager, ResourceManager should remove the old slot allocation from its
own view and mark the slot free. So I think we should keep the following code
in the old SlotManager `updateSlotStatus`:
_else {
// slot is reported empty
// check whether we also thought this slot is
empty
if (allocationMap.isAllocated(slotId)) {
LOG.info("Slot allocation info
mismatch! SlotID:{}, current:{}, reported:null",
slotId,
allocationMap.getAllocationID(slotId));
// we thought the slot is in use,
correct it
allocationMap.removeAllocation(slotId);
// we have a free slot!
handleFreeSlot(slot);
}
}_
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
