hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Duo Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17035) Check why we roll a wal writer at 10MB when the configured roll size is 120M+ with AsyncFSWAL
Date Mon, 07 Nov 2016 10:37:58 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15643798#comment-15643798
] 

Duo Zhang commented on HBASE-17035:
-----------------------------------

requestLogRoll is asynchronous. It just adds an entry in a map in LogRoller. So it is possible
that the requestLogRoll is triggered 3 times with the same writer instance. You can see the
comment in the syncCompleted method in the v1 patch of HBASE-17021.

Thanks.

> 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)

Mime
View raw message