[
https://issues.apache.org/jira/browse/HBASE-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014712#comment-13014712
]
stack commented on HBASE-3719:
------------------------------
bq. It will be nice if we can continue to write new transactions to the new
HLog (but maybe not commit those transactions) while the old HLog is being
closed.
We'd hold up clients while this was going on? We'd not return to clients until
after the commital to the new HLog had gone through?
> Workload has to drain before hlog can be rolled
> -----------------------------------------------
>
> Key: HBASE-3719
> URL: https://issues.apache.org/jira/browse/HBASE-3719
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
>
> In the current implementation, the regionserver blocks new transactions from
> occuring when the HLog is rolled. Closing the existing HLog sometimes takes
> more than a few seconds and during this time all new puts/increments are
> blocked. It will be nice if we can continue to write new transactions to the
> new HLog (but maybe not commit those transactions) while the old HLog is
> being closed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
