Hello Stack, That parameter is for WAL right? I am trying to find a way to achieve reliable persistency in HBase without the WAL slowness, but it looks like impossible ..
On Tue, May 31, 2011 at 11:07 AM, Stack <[email protected]> wrote: > Have you looked at deferred flushing? Its an attribute you set on > your table. You then say how often to run sync using > 'hbase.regionserver.optionallogflushinterval'. Default is sync every > second. > > St.Ack > > On Sat, May 28, 2011 at 6:47 AM, Qing Yan <[email protected]> wrote: > > Well, I realized myself RS flush to HDFS is not designed to do > incremental > > changes. So there is no way around of WAL? man..just wish it can run a > bit > > faster:-P > > > > On Sat, May 28, 2011 at 9:36 PM, Qing Yan <[email protected]> wrote: > > > >> Ok, thanks for the explaination. so data loss is normal in this case. > >> Yeah , I did a "kill -9". I did wait till the RS get reassigned and > >> actually let process B keep retring over the night .. > >> > >> Is WAL the only way to guarantee data safety in hbase? We want high > insert > >> rate though. > >> Is there a middle ground? e.g. a sync operation to flush RS to HDFS will > be > >> perfect! > >> > >> > >>> > >> > > >
