Hi folks, We currently create an OrderedExecutor and an OrderedScheduler in the client. An OrderedScheduler is an OrderedExecutor. Moreover, it's very seldom used (basically for polling LAC, speculative reads and explicit flush.
I propose that we fold these into one. i.e. construct an OrderedScheduler, constructed with the same parameters as we build the OrderedExecutor now, and use this OrderedScheduler for all cases rather than the OrderedExecutor. (this is the first in a bunch of changes I'll be proposing to clean up the client thread model). -Ivan
