Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8F8F719861 for ; Thu, 21 Apr 2016 07:06:06 +0000 (UTC) Received: (qmail 32280 invoked by uid 500); 21 Apr 2016 07:06:06 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 32186 invoked by uid 500); 21 Apr 2016 07:06:06 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 32174 invoked by uid 99); 21 Apr 2016 07:06:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Apr 2016 07:06:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id CE15418023C for ; Thu, 21 Apr 2016 07:06:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id DqiQ37U7g1Ga for ; Thu, 21 Apr 2016 07:06:02 +0000 (UTC) Received: from mail-oi0-f53.google.com (mail-oi0-f53.google.com [209.85.218.53]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id EA7D45F1D5 for ; Thu, 21 Apr 2016 07:06:02 +0000 (UTC) Received: by mail-oi0-f53.google.com with SMTP id k142so71151590oib.1 for ; Thu, 21 Apr 2016 00:06:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=bOcvNYSUEvDYMABMN6C+10+CdhmrNfzy+QydKW8iVyk=; b=PNrhrjhHDBmd9YfNdOpmtU+2ua4NKhpge3ZwKjEm+h2zxOOQhKbG6vnx3n1eQXm5ZA eRaBuszY6MwwRtvaPSQcPG0a3hMTBoFA/3z42PU7FsUcwOnoFCAoCum00Y4nhR+j2eM6 9pHWKo02cd87z0dtg7j8ltZpYHKm0h3qmm1R6U+Bh7WlvdSIpkeJ5SlQkzYX09ZnXycC 8Snmb2uycHPhy6ZIBz141drbaVS4GntuiNKpSzGadTKlaSPig9Z7Ld18PoIiqOTriCAs 7qCsalEJidQ7zjfxZpr/LGKbG9umkqb+tJriflx0/CuRVt7PXRJ8Erfl49E4qHvzvuQn RLew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=bOcvNYSUEvDYMABMN6C+10+CdhmrNfzy+QydKW8iVyk=; b=KDmiFRp89Chbile7q3nosPL2Z1/e9EKBc6qyyAlw1oEXliUrae9vWm5sXTJ2qO1Oyh JbLOHtPWaU4sTjtf1qL+qXVTZfWx+l2n87I0iHKqopL8P4cMrXoTzvsQYvNM34VZFnr2 GHfsyBxDTgYNwSiIjSHnRQmKYgLM1/kgGrXGlNOqhosjNskJ17sv15G1BaQ9WEQW07Vf c3A4lurTZXcClvXWC8pNQpGndrHAO6JHEj29W42VuF72HcSsfcWb1VYRUeMyoFRxD1Pj kr2K8wDuk2hQ9oirvRyYtzQV1hgEimUOfgXq1y/asHaY2itPrDhgqh+S9v/PDxgAO5VE 7JGg== X-Gm-Message-State: AOPr4FWSrE0K5+1751KMDw5xJojJ4FS/qVa9fXK7PSBmU9oDgxIe2d7cAFZaUGVrSOd8AJesFAXYkOE+FOruOA== X-Received: by 10.182.17.9 with SMTP id k9mr5481758obd.3.1461222355849; Thu, 21 Apr 2016 00:05:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.81.144 with HTTP; Thu, 21 Apr 2016 00:05:26 -0700 (PDT) In-Reply-To: References: From: Mikhail Antonov Date: Thu, 21 Apr 2016 00:05:26 -0700 Message-ID: Subject: Re: Allowing clients to set priorities To: "dev@hbase.apache.org" Content-Type: multipart/alternative; boundary=f46d0444745b7558140530f957fd --f46d0444745b7558140530f957fd Content-Type: text/plain; charset=UTF-8 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 (deadline scheduling for RPC requests) in the area of rpc prioritizing. -Mikhail On Wed, Apr 20, 2016 at 11:21 PM, Stack wrote: > On Wed, Apr 20, 2016 at 1:47 PM, rahul gidwani > 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 --f46d0444745b7558140530f957fd--