Causes of a High Memtable Live Ratio

[Caleb Rackliffe <ca...@steelhouse.com>]

Hi All,

>From what I've read in the source, a Memtable's "live ratio" is the ratio of Memtable usage to the current write throughput.  If this is too high, I imagine the system could be in a possibly unsafe state, as the comment in Memtable.java indicates.

Today, while bulk loading some data, I got the following message:

WARN [pool-1-thread-1] 2011-11-18 21:08:57,331 Memtable.java (line 172) setting live ratio to maximum of 64 instead of 78.87903667214012

Should I be worried?  If so, does anybody have any suggestions for how to address it?

Thanks :)

Caleb Rackliffe | Software Developer
M 949.981.0159 | caleb@steelhouse.com
[cid:88029BB7-C464-45DA-94B5-B7188AED39A7]

Re: Causes of a High Memtable Live Ratio

[Jahangir Mohammed <md...@gmail.com>]

Memtable live ratio is fixed between 0 and 64. It's reset to 64 once live
ratio reports a higher value. It's between 0 and 64 for health of the node.
On Nov 19, 2011 6:10 PM, "Caleb Rackliffe" <ca...@steelhouse.com> wrote:

> Hi All,
>
> From what I've read in the source, a Memtable's "live ratio" is the ratio
> of Memtable usage to the current write throughput.  If this is too high, I
> imagine the system could be in a possibly unsafe state, as the comment in
> Memtable.java indicates.
>
> Today, while bulk loading some data, I got the following message:
>
> WARN [pool-1-thread-1] 2011-11-18 21:08:57,331 Memtable.java (line 172)
> setting live ratio to maximum of 64 instead of 78.87903667214012
>
> Should I be worried?  If so, does anybody have any suggestions for how to
> address it?
>
> Thanks :)
>
> *
> Caleb Rackliffe | Software Developer
> M 949.981.0159 | caleb@steelhouse.com
> **
> *
>