<property>
<name>hbase.regionserver.optionalcacheflushinterval</name>
<value>1800000</value>
<description>
Amount of time to wait since the last time a region was flushed before
invoking an optional cache flush (An optional cache flush is a
flush even though memcache is not at the memcache.flush.size).
Default: 30 minutes (in miliseconds)
</description>
</property>
On Wed, Sep 23, 2009 at 1:41 PM, stack <st...@duboce.net> wrote:
> Whats the option name Clint? I just checked out 0.19.0 and had a look in
> hbase-default to try and jog my memory but I'm not sure which setting it is
> (was).
>
> To force a flush you could do below in a cron job?
>
> echo "flush 'TABLENAME'" | ./bin/hbase shell
>
> ... or variations thereof.
>
> St.Ack
>
>
> On Wed, Sep 23, 2009 at 1:23 PM, Clint Morgan <cm-pub...@troove.net>
> wrote:
>
> > Is there no optional memstore flush anymore? I recall in 0.19 the
> memcache
> > would flush every so-often and you could configure this period (optional
> > cache flush interval).
> >
> > Digging through now, I don't see it in 0.20. Is this mechanism no longer
> > supported?
> >
> > Due to a couple of mixups, our stop cluster, take backup, restart cluster
> > mechanism had stopped running for a while. So we were not force-flushing,
> > nor generating enough data to flush.
> > Then we had a crash and I realized that the on-file stores were missing
> > writes from weeks ago. I eventually got the data back from the WAL.
> >
> > cheers,
> > -clint
> >
>
