[
https://issues.apache.org/jira/browse/HBASE-11028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974402#comment-13974402
]
stack commented on HBASE-11028:
-------------------------------
+1
I think start with this.
Later, we might look at doing same at other side of the ringbuffer. Currently
it would be complicated to do. On other side of the ringbuffer, we just append
the edit. The edit has disappeared into the WAL. The sync has not been called
yet. Handlers are currently tied to their sync via the SyncFuture. We'd have
to add a listing of a Handlers' seqid to the SyncFuture. It'd be messy
currently.
This stuff will change again soon; e.g. the Himanshu switch writers and then
multiwal hopefully. Maybe come back to this issue then. There may be more
points we can make use of after these refactorings.
> FSLog: Avoid an extra sync if the current transaction is already sync'd
> -----------------------------------------------------------------------
>
> Key: HBASE-11028
> URL: https://issues.apache.org/jira/browse/HBASE-11028
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.99.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Fix For: 0.99.0
>
> Attachments: 11028.v1.patch
>
>
> See HBASE-10156.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
