[
https://issues.apache.org/jira/browse/HBASE-17035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646531#comment-15646531
]
ramkrishna.s.vasudevan commented on HBASE-17035:
------------------------------------------------
One more query on the operation of syncFutures.
in finishSync() that gets called asynchronously we peek and then remove from
the syncFutures. So we add to syncFutures in a synchronized block but we remove
it asynchronously. So will this have an impact? How ever once we mark the
syncFuture as done then the blocking thread on sync will get released. But will
this comparator logic will work fine now since syncFuture is now a
PriorityQueue? In FSHLog it is LinkedBlockingqueue.
> Check why we roll a wal writer at 10MB when the configured roll size is 120M+
> with AsyncFSWAL
> ---------------------------------------------------------------------------------------------
>
> Key: HBASE-17035
> URL: https://issues.apache.org/jira/browse/HBASE-17035
> Project: HBase
> Issue Type: Sub-task
> Components: wal
> Affects Versions: 2.0.0
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Fix For: 2.0.0
>
>
> Found this when addressing HBASE-16890. It is one of the possible reason that
> why AsyncFSWAL performs worse than FSHLog when running PE tool.
> https://issues.apache.org/jira/browse/HBASE-16890?focusedCommentId=15636688&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15636688
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
