[
https://issues.apache.org/jira/browse/HBASE-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479481#comment-13479481
]
stack commented on HBASE-7011:
------------------------------
Is the special COMPLETE_CACHE_FLUSH edit even used anywhere?
> log rolling and cache flushing should be able to proceed in parallel
> --------------------------------------------------------------------
>
> Key: HBASE-7011
> URL: https://issues.apache.org/jira/browse/HBASE-7011
> Project: HBase
> Issue Type: Improvement
> Reporter: Kannan Muthukkaruppan
> Assignee: Kannan Muthukkaruppan
>
> Today, during a memstore flush (snapshot of memstore + flushing to disk), log
> rolling cannot happen. This seems like a bad design, and an unnecessary
> restriction.
> Possible reasons cited for this in code are:
> (i) maintenance of the lastSeqWritten map.
> (ii) writing a "completed-cache-flush" marker into the same log before the
> roll.
> It seems that we can implement a new design for (i) to avoid holding the lock
> for the entire duration of the flush. And the motivation for (ii) is not even
> clear. We should reason this out, and make sure we can relax the restriction.
> [See related discussion in HBASE-6980.]
--
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
