Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A084118146 for ; Wed, 20 May 2015 02:04:30 +0000 (UTC) Received: (qmail 32737 invoked by uid 500); 20 May 2015 02:04:28 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 32669 invoked by uid 500); 20 May 2015 02:04:28 -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 32657 invoked by uid 99); 20 May 2015 02:04:28 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 May 2015 02:04:28 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id A8468C63B2 for ; Wed, 20 May 2015 02:04:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.756 X-Spam-Level: * X-Spam-Status: No, score=1.756 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-1.143, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id qqc64pSxiQko for ; Wed, 20 May 2015 02:04:27 +0000 (UTC) Received: from mail-ob0-f175.google.com (mail-ob0-f175.google.com [209.85.214.175]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id D192024BB6 for ; Wed, 20 May 2015 02:04:26 +0000 (UTC) Received: by obfe9 with SMTP id e9so26408568obf.1 for ; Tue, 19 May 2015 19:04:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=9qYKsBGq1OXXea1iYN1l4UrMK3H+JYo6YyvBOMO+Jes=; b=NLaPzJV/Hx78WsSCujFd7UmTShwz6PMEhKvWfslhtS+9TIbIjc89nb0JplBrBiyhj8 o1DSpdOwEetWTb6q9h4gEMeOR5rAlnOsg0a6sL3Ks06wqajNJQ/1OiW/rwIdXl8U0olk O7JAAnPrw3yjjCreDUddIFodZ9ZK9+JHzhV/k5VaNdZci/JgkPOLBmiNqlOIJzWhTVlU bt95Ntkw13OX9q56pWbm8T5lGB8Tz1QQ2huSTw6+Je9A839gtXDxxlKuL4XQe7i2q3jO QQ7CDwWXS+nlfxLmMVSdK9ZRaoCsfRTxIGAqtKnsaQ3Tn2+PFbWwjIndA6snrUVf+2n4 PQ0w== MIME-Version: 1.0 X-Received: by 10.182.142.137 with SMTP id rw9mr26970393obb.83.1432087460057; Tue, 19 May 2015 19:04:20 -0700 (PDT) Received: by 10.202.177.2 with HTTP; Tue, 19 May 2015 19:04:19 -0700 (PDT) In-Reply-To: <3fe21a95.131e1.14d6ef32271.Coremail.c77_cn@163.com> References: <397b8c9c.62a5.14d4b2663e1.Coremail.c77_cn@163.com> <299d92ec.d243.14d64fe4ff2.Coremail.c77_cn@163.com> <3fe21a95.131e1.14d6ef32271.Coremail.c77_cn@163.com> Date: Tue, 19 May 2015 19:04:19 -0700 Message-ID: Subject: Re: Re: Re: How to know the root reason to cause RegionServer OOM? From: Ted Yu To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a11c33a02581a2e051679d859 --001a11c33a02581a2e051679d859 Content-Type: text/plain; charset=UTF-8 For scenario #1, you would see in the regionserver.out file that "kill -9 " command was applied due to OOME. For scenario #2, can you see if dmesg provides some clue ? Cheers On Tue, May 19, 2015 at 6:32 PM, David chen wrote: > Thanks for guys reply, its indeed helped me. > Another question, I think there are two possibilities to kill RegionServer > process: > 1. When JVM inspects that the memory, RegionServer has occupied, exceed > the max-heap-size, then JVM calls positively the command configured by > option "-XX:OnOutOfMemoryError=kill -9 %p" to kill RegionServer process. > 2. RegionServer process does not reach the max-heap-size, but new > application need to allocation memory, if lack of memory, OS will choose > to kill some processes, RegionServer unfortunately becomes the first > choice, so it is killed by OS. > Is my understanding right? If so, how to know which possibility my scene > is? > Any ideas can be appreciated! > --001a11c33a02581a2e051679d859--