[
https://issues.apache.org/jira/browse/HBASE-17035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15643540#comment-15643540
]
Duo Zhang commented on HBASE-17035:
-----------------------------------
Where do you get the length? If it is writer.getLength then it is possible. If
there are multiple out-going sync requests then it is possible that when they
come back they all see the writer.getLength is larger than the logrollsize. But
this will not cause multiple rolls as the requests from same WAL will be stored
only once in log roller. There is a map in log roller.
> 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)
