|| at Jun 17, 2016 at 9:30 pm
so what you're saying is that everyone will see at least 1 of those lines
roughly every hour no matter what, and under higher load you'll see it when
ever limits are hit for either WAL or Memstore causing flushes.
So by the sounds of it, it's perfectly normal to be seeing a slew of those
in the log files and they can more or less be safely ignore.
On Fri, Jun 17, 2016 at 12:52 PM, Vladimir Rodionov wrote:
This is done to prevent runaway WAL files. WAL file can't be deleted if
some unflushed edits from this file exist in RS memstore.
In case of a high load this may lead to accumulation of a large number of
WAL files in a file system.
On Fri, Jun 17, 2016 at 12:49 PM, Vladimir Rodionov <firstname.lastname@example.org
Yes, this is what PeriodicMemstoreFlusher does: it checks if there are
edits older than (1h, but configurable) in memstore
and flushes this memstore if find old edits.
On Fri, Jun 17, 2016 at 11:49 AM, Ted wrote:
Wondering if anyone knows the cause of messages like :
"MemstoreFlusherChore requesting flush of
<COLUMN_FAMILY> has an old edit so flush to free WALs after random delay
My log files seem to be filled with them, I think they account for over
of the lines in my log files.