Return-Path: X-Original-To: apmail-accumulo-user-archive@www.apache.org Delivered-To: apmail-accumulo-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 3ED1711BC7 for ; Wed, 18 Jun 2014 17:13:47 +0000 (UTC) Received: (qmail 36112 invoked by uid 500); 18 Jun 2014 17:13:47 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 36054 invoked by uid 500); 18 Jun 2014 17:13:47 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 36044 invoked by uid 99); 18 Jun 2014 17:13:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2014 17:13:46 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of eric.newton@gmail.com designates 209.85.216.48 as permitted sender) Received: from [209.85.216.48] (HELO mail-qa0-f48.google.com) (209.85.216.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2014 17:13:41 +0000 Received: by mail-qa0-f48.google.com with SMTP id x12so961727qac.35 for ; Wed, 18 Jun 2014 10:13:21 -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=aN0n1n2J5YV05Idf+J55PEsXFXk8xUB7JLkGM6lJ0J8=; b=XqiP14OwJb+JxkjvqDoJrmYdwYNG4k64pd0j/U9H4lJ5KgCR6m+4AbwlP3m5bLG/k3 tPhOOuc0FoY7UjyIAnwA6RFMjj3EkbmHZ2bhAHZOMuRw4PmX/+KwiOhEP/PAt3EhIh2a pzfB37nKj1N/NyYCVGg7m9KklzDK+doMAoADtRP2V9WyW60flqupiSeBjU84IYdsvqG8 k6Xn/QWHXesyY6i1DREnv2nLXjj+gnmAZKKi+ZkahyYysJiYoE8tm6uG13wSOlOR8Ykp s2eKO6pZbJWp0jBE/XFDarnuzKqxRWH0CRfU/nV15WLj5YjtDZNC3Nuy6eApnDUverDZ fyJQ== MIME-Version: 1.0 X-Received: by 10.140.33.200 with SMTP id j66mr4794363qgj.81.1403111601117; Wed, 18 Jun 2014 10:13:21 -0700 (PDT) Received: by 10.96.34.197 with HTTP; Wed, 18 Jun 2014 10:13:21 -0700 (PDT) In-Reply-To: References: <53A11987.5080003@gmail.com> <53A1C2EF.7070504@gmail.com> Date: Wed, 18 Jun 2014 13:13:21 -0400 Message-ID: Subject: Re: MutationsRejectedException and TApplicationException From: Eric Newton To: "user@accumulo.apache.org" Content-Type: multipart/alternative; boundary=001a113a8e14909f4b04fc1f607f X-Virus-Checked: Checked by ClamAV on apache.org --001a113a8e14909f4b04fc1f607f Content-Type: text/plain; charset=UTF-8 Yes... keeping MaxNewSize small reduces the time to collect the New Generation, which is a stop-the-world gc. 32G max jvm runtime is probably excessive if you are using the native map (since it doesn't take up JVM memory). Check the gc lines in your tserver debug log to see how much of the JVM memory you are actually using. -Eric On Wed, Jun 18, 2014 at 1:04 PM, Jianshi Huang wrote: > I see. thank you Josh and Eric. > > BTW, here's my current JVM memory settings: -Xmx32g -Xms4g -XX:NewSize=2G > -XX:MaxNewSize=2G (Xmx < 32g for enabling CompressedOops by default) > > Is 2G good enough for MaxNewSize? > > > Cheers, > Jianshi > > > On Thu, Jun 19, 2014 at 12:54 AM, Eric Newton > wrote: > >> >> On Wed, Jun 18, 2014 at 12:51 PM, Jianshi Huang >> wrote: >> >>> Oh, this memory size: >>> >>> tserver.memory.maps.max >>> 1G -> 20G (looks like this is an overkill, is it?) >>> >> >> Probably. If you have a spare 20G, though... :-) >> >> >>> >>> tserver.cache.data.size >>> 128M? -> 1024M >>> >>> tserver.cache.index.size >>> 128M? -> 1024M >>> >> >> These will help with query, not ingest. >> >> >> > > > -- > Jianshi Huang > > LinkedIn: jianshi > Twitter: @jshuang > Github & Blog: http://huangjs.github.com/ > --001a113a8e14909f4b04fc1f607f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yes... keeping MaxNewSize small reduces the time to c= ollect the New Generation, which is a stop-the-world gc.

= 32G max jvm runtime is probably excessive if you are using the native map (= since it doesn't take up JVM memory).

Check the gc lines in your tserver debug log to see how much= of the JVM memory you are actually using.

-Er= ic


On Wed, Jun 18, 2014 at 1:04 PM, Jianshi Huang <jianshi.huang@gmail.= com> wrote:
I see. thank you Josh and Eric.

BTW, he= re's my current JVM memory settings:=C2=A0-Xmx32g -Xms4g -XX:NewSize=3D= 2G -XX:MaxNewSize=3D2G (Xmx < 32g for enabling CompressedOops by default= )

Is 2G good enough for MaxNewSize?

<= br>
Cheers,
Jianshi


On Thu, Jun 19= , 2014 at 12:54 AM, Eric Newton <eric.newton@gmail.com> = wrote:
=
On Wed, Jun 18, 2014 at 12:51 PM, Jians= hi Huang <jianshi.huang@gmail.com> wrote:
Oh, this memory size:
<= br>
tserver.memory.maps.max
1G -> 20G (looks lik= e this is an overkill, is it?)

Probably.=C2=A0 If you have a = spare 20G, though... :-)
=C2=A0

tserver.cache.data.size
128M? -> 1024M=

tserver.cache.index.size
128M? -> 1024= M

These will help with qu= ery, not ingest.
=C2=A0




--
Jianshi Huang

LinkedIn: jianshi
Twitter: @jshuang=
Github & Blog: http://huangjs.github.com/

--001a113a8e14909f4b04fc1f607f--