[ https://issues.apache.org/jira/browse/HBASE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HBASE-5930: ------------------------------- Attachment: 5930-0.94-added-addendum-with-tests.txt Patch for 0.94 with the latest config/tests changes. > Limits the amount of time an edit can live in 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 > Fix For: 0.98.0, 0.94.8, 0.95.1 > > Attachments: 5930-0.94-2.txt, 5930-0.94-added-addendum.txt, > 5930-0.94-added-addendum-with-tests.txt, 5930-0.94.txt, 5930-1.patch, > 5930-2.1.patch, 5930-2.2.patch, 5930-2.3.patch, 5930-2.4.patch, > 5930-addendum-for-disabling.trunk.txt, > 5930-addendum-for-disabling.trunk.with-tests.txt, > 5930-addendum-for-disabling.trunk.with-tests.txt, > 5930-track-oldest-sample.txt, 5930-wip.patch, HBASE-5930-ADD-0.patch, > hbase-5930-addendum2.patch, hbase-5930-test-execution.log > > > 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