Resource leak when async scheduling is enabled

Brief steps to reproduce

1. Enable async scheduling, 5 threads
2. Submit a lot of jobs trying to exhaust cluster resource
3. After a while, observed NM allocated resource is more than resource requested by allocated containers

Looks like the commit phase is not sync handling reserved containers, causing some proposal incorrectly accepted, subsequently resource was deducted multiple times for a container.