[
https://issues.apache.org/jira/browse/HBASE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563225#comment-13563225
]
Devaraj Das commented on HBASE-5930:
------------------------------------
bq. I think the delay should algorithmically related to the flush interval
I think what I currently have has a certain advantage - like if the configured
value of cacheflushinterval is too low or something, the chore will be
triggered very often but the sleep interval (0 - 2 minutes) would keep the
#flushes under control. But yeah, I can always enforce a minimum delay before
each flush.
bq. Could we fold the jitter into shouldFlush() rather than actually waiting in
chore()?
I think that shouldFlush shouldn't be involved in determining how much to delay
the flush. Do you see any issues in waiting in the chore?
> Periodically flush the Memstore?
> --------------------------------
>
> Key: HBASE-5930
> URL: https://issues.apache.org/jira/browse/HBASE-5930
> Project: HBase
> Issue Type: Improvement
> Reporter: Lars Hofhansl
> Assignee: Devaraj Das
> Priority: Minor
> Fix For: 0.96.0
>
> Attachments: 5930-1.patch, 5930-2.1.patch, 5930-wip.patch
>
>
> A colleague of mine ran into an interesting issue.
> He inserted some data with the WAL disabled, which happened to fit in the
> aggregate Memstores memory.
> Two weeks later he a had problem with the HDFS cluster, which caused the
> region servers to abort. He found that his data was lost. Looking at the log
> we found that the Memstores were not flushed at all during these two weeks.
> Should we have an option to flush memstores periodically. There are obvious
> downsides to this, like many small storefiles, etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
