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 4A610200CF8 for ; Wed, 26 Jul 2017 06:13:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 491BA1681B8; Wed, 26 Jul 2017 04:13:09 +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 9626F1681B4 for ; Wed, 26 Jul 2017 06:13:08 +0200 (CEST) Received: (qmail 23464 invoked by uid 500); 26 Jul 2017 04:13:07 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 23435 invoked by uid 99); 26 Jul 2017 04:13:07 -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; Wed, 26 Jul 2017 04:13:07 +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 10F2618070B for ; Wed, 26 Jul 2017 04:13:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-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 XOc2gT7qWRjh for ; Wed, 26 Jul 2017 04:13:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 8F8B361109 for ; Wed, 26 Jul 2017 04:13:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 463D9E0E4A for ; Wed, 26 Jul 2017 04:13:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id CB94923F77 for ; Wed, 26 Jul 2017 04:13:00 +0000 (UTC) Date: Wed, 26 Jul 2017 04:13:00 +0000 (UTC) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18023) Log multi-* requests for more than threshold number of rows MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 26 Jul 2017 04:13:09 -0000 [ https://issues.apache.org/jira/browse/HBASE-18023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101144#comment-16101144 ] Hudson commented on HBASE-18023: -------------------------------- FAILURE: Integrated in Jenkins build HBase-2.0 #234 (See [https://builds.apache.org/job/HBase-2.0/234/]) HBASE-18023 Update row threshold warning from 1k to 5k (addendum) (elserj: rev 50d930113672697eff6f3b9f35b6bbd35cfd6262) * (edit) hbase-common/src/main/resources/hbase-default.xml * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java > Log multi-* requests for more than threshold number of rows > ----------------------------------------------------------- > > Key: HBASE-18023 > URL: https://issues.apache.org/jira/browse/HBASE-18023 > Project: HBase > Issue Type: Improvement > Components: regionserver > Reporter: Clay B. > Assignee: David Harju > Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2 > > Attachments: HBASE-18023.addendum.patch, HBASE-18023-branch-1.3.patch, HBASE-18023-branch-1.patch, HBASE-18023.master.001.patch, HBASE-18023.master.002.patch, HBASE-18023.master.003.patch, HBASE-18023.master.004.patch > > > Today, if a user happens to do something like a large multi-put, they can get through request throttling (e.g. it is one request) but still crash a region server with a garbage storm. We have seen regionservers hit this issue and it is silent and deadly. The RS will report nothing more than a mysterious garbage collection and exit out. > Ideally, we could report a large multi-* request before starting it, in case it happens to be deadly. Knowing the client, user and how many rows are affected would be a good start to tracking down painful users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)