Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates
 209.85.210.169 as permitted sender)
MIME-Version: 1.0
Sender: jdcryans@gmail.com
In-Reply-To: <1A27A630-AFB6-4E64-B8EF-F57494611AC3@gmail.com>
References: 
 <CANrHeErx73jsTofFgt+q2TZFM7RVve3QHf2E0CivfDyFEO9vwA@mail.gmail.com>
	<CADcMMgHSaWMtziVBiUVbhXRE42DF=5GZhTBTMifam6bVYjx5Pw@mail.gmail.com>
	<218E1393-4B8C-445D-93E6-AF23E6038D9D@gmail.com>
	<CAGpTDNcNbaGqxhd046TW5M1vz062Q2wbR2eRrLdkRiDARyr7=A@mail.gmail.com>
	<D3E03433-9843-4830-BE45-DB1C3D4BD2C1@gmail.com>
	<CAGpTDNcTpe1wddf23+tZX+YY4A5xshSfZ4BaifKFFpH03pACmA@mail.gmail.com>
	<DC6D9DAA-93D1-4744-B297-013E8D7CE2C4@gmail.com>
	<CAGpTDNfENmS3bx-UCQQLUsFu40KJVkL0hiQQAOq8rZU+noenkw@mail.gmail.com>
	<6C49424F-8751-429E-A2AE-7D9F132CCF87@gmail.com>
	<CAGpTDNdxi=SAwfDC1wiq4T6Y3fGkzCO6AoqzOpp4NdgFGDJw5w@mail.gmail.com>
	<1A27A630-AFB6-4E64-B8EF-F57494611AC3@gmail.com>
Date: Tue, 7 Feb 2012 09:25:10 -0800
Message-ID: 
 <CAGpTDNcbsGsMBuS29ZrDNCpWqY8T4ssu1XnLo-W3HX56W4oTpA@mail.gmail.com>
Subject: Re: xceiver count, regionserver shutdown
From: Jean-Daniel Cryans <jdcryans@apache.org>
To: user@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hurray! Thanks for following up, I really appreciate it. The upload
speed should be better too.

I should some time to write this all down in a more readable format
for the reference guide on the website.

J-D

On Tue, Feb 7, 2012 at 5:13 AM, Bryan Keller <bryanck@gmail.com> wrote:
> Just to follow up, this did indeed fix the problem I was having with hitt=
ing the xceiver limit. Thanks a bunch for the help, I have a much better un=
derstanding of how heap, memstore size, and number of regions all play a ro=
le in performance and resource usage.
>
> On Feb 6, 2012, at 5:03 PM, Jean-Daniel Cryans wrote:
>
>> On Mon, Feb 6, 2012 at 4:47 PM, Bryan Keller <bryanck@gmail.com> wrote:
>>> I increased the max region file size to 4gb so I should have fewer than=
 200 regions per node now, more like 25. With 2 column families that will b=
e 50 memstores per node. 5.6gb would then flush files of 112mb. Still not c=
lose to the memstore limit but shouldn't I be much better off than before?
>>
>> Ah sorry I didn't understand that you were restarting with a new
>> table. In that case go with even fewer regions and if you aren't
>> relying on the block cache for anything fast reads then you could also
>> expend the memstore global usage.
>>
>>> Inserting sequentially may or may not be an option for me. I am storing=
 a live feed of data from an external source so it could prove tricky.
>>
>> Thought so.
>>
>> J-D
>