Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2993E200D08 for ; Tue, 8 Aug 2017 07:03:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 28120166B5A; Tue, 8 Aug 2017 05:03:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4763B166B54 for ; Tue, 8 Aug 2017 07:03:05 +0200 (CEST) Received: (qmail 20668 invoked by uid 500); 8 Aug 2017 05:03:03 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 20646 invoked by uid 99); 8 Aug 2017 05:03:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Aug 2017 05:03:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 10E64C02A9; Tue, 8 Aug 2017 05:03:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.379 X-Spam-Level: X-Spam-Status: No, score=0.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id YPS2Z_RV_9j3; Tue, 8 Aug 2017 05:02:58 +0000 (UTC) Received: from mail-yw0-f169.google.com (mail-yw0-f169.google.com [209.85.161.169]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 5C0335F6C8; Tue, 8 Aug 2017 05:02:57 +0000 (UTC) Received: by mail-yw0-f169.google.com with SMTP id s143so14728305ywg.1; Mon, 07 Aug 2017 22:02:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BWvkqxM6AIpyE+9FMLtLg1961yYH+5Nd5yY/nEqHPeo=; b=YzwpDVdqt2ejYnxMoY7+7XU2JCyt5dA1b3bN6qy83HpYLrgPnYC/mdBbfpgxFdQNS8 NCOqFle9kFU8B6mSLKK1nbK5U0I01niQpCDxKbFvr1eQdDE3lPa8N9DEQ03lkQXpg30M hnD0/c0B05oHqFr4D23tWa2atwU16yOkvTVZIS1Xw8rJupem3crQ75wuehJoRdJtLh9w N8KWjq0U7P1qkk4XT54/vZFYnkmspf7MU/VY7pIsn2Lo5k8YACm3Zgp3r13aALf0fjgu Sq5AeW4MIXoOGp5kMrHYJfkCdfdQZ00GIb7L+Ea4qNKIpPU8M+vEXbk+qPJ9XW4s3AT9 nPyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BWvkqxM6AIpyE+9FMLtLg1961yYH+5Nd5yY/nEqHPeo=; b=YqAtjW/xT0jhc6QPXoE2+aaESNQWyji2w3nDHi71sofRWomU0fZsMwvgnBxNp0HIQe KUDkzXzTY7cLvoXi9psii9D1mcjrtR3kz4xCr3MSn7GJFp5j552l9ohTc1tLHQqxOYWr 9PYZSalfMIGz+9NZmPcWHWxiMzHzRRfWQO5deTOm4gWAPXP8UqQRIOzOglwMLOePTP7N FOVGFILWygXJxheiZ6p91D5ROzGiuH5AMU9J6BzsVdT4oUOaWS1caIpaV+bi/RrZyXET St0ttW9UEdNQKhMaD61JfdQauTS0N5vHOp7/yySgBI01/AW9yiSPvNP960wWpOyv52iM kNXA== X-Gm-Message-State: AHYfb5jyCxN0SNiMFpPNKzjsqP1O9yZXPkP89LTmXVRx63KKIeBO0y95 /Ec3ecn6rbonvdUibhX/MwmMd+60ohhN X-Received: by 10.37.47.66 with SMTP id v63mr2296098ybv.91.1502168576007; Mon, 07 Aug 2017 22:02:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.13.211.199 with HTTP; Mon, 7 Aug 2017 22:02:55 -0700 (PDT) In-Reply-To: References: From: Anoop John Date: Tue, 8 Aug 2017 10:32:55 +0530 Message-ID: Subject: Re: [DISCUSS] Planning changes on RegionServer totalRequestCount metrics To: "user@hbase.apache.org" Cc: "dev@hbase.apache.org" Content-Type: text/plain; charset="UTF-8" archived-at: Tue, 08 Aug 2017 05:03:06 -0000 I see.. Good... Ya +1 On Tue, Aug 8, 2017 at 8:46 AM, Yu Li wrote: > Thanks for chiming in @Anoop. Jerry raised the same question in JIRA and > the patch is already updated there, will rename the metrics to > "totalRowActionRequestCount". Will add release note to make it clear for > user what the final changes are > > Best Regards, > Yu > > On 7 August 2017 at 15:19, Anoop John wrote: > >> Sorry for being late here Yu Li. >> Regarding counting the rows (for the new metric) in multi.. There >> might be 2 Actions in multi request for the same row. This is possible >> some time. I dont think we should check that and try to make it >> perfect. That will have perf penalty also. So just saying that we >> will have some possible inconsistency even after. May be we can say >> how many actions in multi not rows affected! any better name ? >> >> On Mon, Aug 7, 2017 at 8:07 AM, Yu Li wrote: >> > Thanks for chiming in @stack and @Jerry, will try to add a good release >> > note when the work done. >> > >> > Since already more than 72 hours passed and no objections, I'd like to >> call >> > this discussion closed and apply the change in HBASE-18469. Thanks. >> > >> > Best Regards, >> > Yu >> > >> > On 4 August 2017 at 13:59, stack wrote: >> > >> >> +1 >> >> >> >> We need a fat release note on this change so operators can quickly learn >> >> why traffic went down on upgrade. >> >> >> >> S >> >> >> >> On Aug 3, 2017 14:49, "Yu Li" wrote: >> >> >> >> > Dear all, >> >> > >> >> > Recently in HBASE-18469 > >> jira/browse/HBASE-18469 >> >> > > >> >> > we found some inconsistency on regionserver request related metrics, >> >> > including: >> >> > 1. totalRequestCount could be less than readRequestCount+ >> >> writeRequestCount >> >> > 2. For multi request, we count action count into totalRequestCount, >> while >> >> > for scan with caching we count only one. >> >> > >> >> > To fix the inconsistency, we plan to make below changes: >> >> > 1. Make totalRequestCount only counts rpc request, thus multi request >> >> will >> >> > only count as one for totalRequestCount >> >> > 2. Introduce a new metrics in name of "totalRowsRequestCount", which >> will >> >> > count the DML workloads on RS by row-level action, and for this >> metrics >> >> we >> >> > will count how many rows included for multi and scan-with-caching >> >> request. >> >> > >> >> > After the change, there won't be any compatibility issue -- existing >> >> > monitoring system could still work -- only that totalRequestCount >> will be >> >> > less than previous. And it's recommended to use totalRowsRequestCount >> to >> >> > check the RS DML workload. >> >> > >> >> > Please kindly let us know if you have any different idea or suggestion >> >> > (operators' opinion is especially welcomed). >> >> > >> >> > Let's make this discussion open for 72 hours and will make the change >> if >> >> no >> >> > objections. >> >> > >> >> > Thanks! >> >> > >> >> > Best Regards, >> >> > Yu >> >> > >> >> >>