"Memory sizing" generally means how much RAM you have allocated to HBase.
The amount of heap, the total size of your memstores and the number of
them. This will impact the size of an individual memstore and thus the size
of the new HFiles flushed to disk. This impacts the frequency and character
of compactions. More column families => more memstores => (usually) smaller
flush sizes => more compactions.
On Mon, Feb 3, 2014 at 4:34 AM, yanivG <[EMAIL PROTECTED]> wrote:
> Hi Kevin,
> 1. No I am not doing bulk loads.
> 2. I don't know. Where can I see this metric? the load is about 200
> per second * 5K of data.
> 3. I don't know.
> Memory sizing? You mean heap size, etc?
> View this message in context:
> Sent from the HBase Developer mailing list archive at Nabble.com.