Il gio 23 ago 2018, 12:09 Ivan Kelly <iv...@apache.org> ha scritto: > 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. >
Why do they exist? Are they only legacy from past or is there any specific reason? Is there any per ledger ordering requirement that we will break (or cause deadlock) if we have a single queue per ledger? These are my only two concerns. Overall the idea makes sense to me and I will support it Enrico > 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 > -- -- Enrico Olivelli
