Ceph » dmclock

The issue that clients aren't scheduled happens after PushPriorityQueue::schedule_request() is processed in PushPriorityQueue::run_sched_ahead(). This is also reproduced with the following scenario.

- Set reservation=1, weight=1, limit=1 (e.g., relatively low value is a conditon that triggers PushPriorityQueue::run_sched_ahead().)
- Enqueue three client requests through PushPriorityQueue::add_request().
- The first request is enqueued and then scheduled right after PushPriorityQueue::schedule_request() is processed.
- The second request is set to be scheduled after 1 second and the third request is enqueued and waits to be scheduled after the second request.
- After 1 second, the second request is serviced by PushPriorityQueue::run_sched_ahead() and the sched_ahead_when is set to TimeZero.
- The problem is that even though requests are waiting at this point, they are not scheduled until PushPriorityQueue::add_request() or PushPriorityQueue::request_completed() is called.