[
https://issues.apache.org/jira/browse/HBASE-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086846#comment-13086846
]
stack commented on HBASE-4224:
------------------------------
An important bit I left off the top is that this 'flush by regionserver' needs
to also clean up WAL logs too after the flushing is done. If everything has
been flushed, then should be able to clean up any outstanding WAL logs.
Scenario is the following. Your hosting service tells you that they are going
to do a risky operation that could cause you to lose network connectivity or
power to your racks. You know that a disaster may be coming and you want to
mitigate the damage.
A facility that flushed and cleaned up all WAL logs by the regionserver (so
could throttle i/o) so if bad crash there is little to replay is what I'm
talking about here.
> Need a flush by regionserver rather than by table option
> --------------------------------------------------------
>
> Key: HBASE-4224
> URL: https://issues.apache.org/jira/browse/HBASE-4224
> Project: HBase
> Issue Type: Bug
> Components: shell
> Reporter: stack
>
> This evening needed to clean out logs on the cluster. logs are by
> regionserver. to let go of logs, we need to have all edits emptied from
> memory. only flush is by table or region. We need to be able to flush the
> regionserver. Need to add this.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
