Github user tison1 commented on the issue:
https://github.com/apache/flink/pull/6360
@shuai-xu
It makes sense.
The message that TM has successfully allocated slot might lost in transport.
When slot manager receives a slot status report which says one slot has
allocation id irrelevant to this offer, then the slot is allocated to another
slot request.
It looks this PR prevents runtime from some potential resource leak,
doesn't it?---
