This is interesting idea. Sorry if I missed some context - what's the primary incentive here? What's examples of those categorized thread pools?
Sounds intersecting a bit with HBASE-15136 <https://issues.apache.org/jira/browse/HBASE-15136> (deadline scheduling for RPC requests) in the area of rpc prioritizing. -Mikhail On Wed, Apr 20, 2016 at 11:21 PM, Stack <st...@duboce.net> wrote: > On Wed, Apr 20, 2016 at 1:47 PM, rahul gidwani <rahul.gidw...@gmail.com> > wrote: > > > I was wondering if people would be interested in allowing the client to > > specify priorities? I really think we are good responsible adults and > wont > > abuse this feature. :) > > > > This would not just be for one particular operation but all operations. > > I'll make it feature complete. > > > > > Sounds sweet. > > RPC passes priority in the header already IIRC. > > We could then purge our ugly decompose of the request just to figure what > it is so we can prioritize based off annotation. > > St.Ack > > > > > As for batch operations prioirites would be at batch level. > > > > I know the phoenix guys would really like this feature as it would really > > help with their indexing work. > > > > > > Eventually I think it would be nice to get to a point where we can have > > some sort of configurable reservation system. Where regionservers could > > have handler groups and we could send a little bit more info with the rpc > > call to specify the reserved set of handlers they would like to utilize. > > > > thanks > > rahul > > > -- Thanks, Michael Antonov
