[
https://issues.apache.org/jira/browse/HBASE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267831#comment-13267831
]
Todd Lipcon commented on HBASE-5930:
------------------------------------
bq. Maybe add a boolean to the memstore to track if it contains edits that were
not written to the WAL
HBASE-5886 adds code which tracks how much un-WAL-ed data is in the memstore.
bq. Meaning that your data in the WAL can only be sitting there for so long.
But if we retain 20 or so HLogs, and we roll only every hour, then we still
have 20 hours worth of data sitting there unflushed, which might be a little
strange if the cluster is entirely idle.
> Periodically flush the Memstore?
> --------------------------------
>
> Key: HBASE-5930
> URL: https://issues.apache.org/jira/browse/HBASE-5930
> Project: HBase
> Issue Type: Improvement
> Reporter: Lars Hofhansl
> Priority: Minor
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
