hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chance Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19344) improve asyncWAL by using Independent thread for netty #IO in FanOutOneBlockAsyncDFSOutput
Date Mon, 27 Nov 2017 02:31:00 GMT

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

Chance Li commented on HBASE-19344:
-----------------------------------

Thanks. sir
Is it possible that we encounter this situation: #createWriterInstance is ok but #flush is
fail.
or is it necessary to do some protect on exception situation like this?
It's maybe a tradeoff about boundary between with HDFS.

> improve asyncWAL by using Independent thread for netty #IO in FanOutOneBlockAsyncDFSOutput

> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-19344
>                 URL: https://issues.apache.org/jira/browse/HBASE-19344
>             Project: HBase
>          Issue Type: Sub-task
>          Components: wal
>    Affects Versions: 2.0.0-beta-1
>            Reporter: Chance Li
>            Assignee: Chance Li
>             Fix For: 2.0.0
>
>         Attachments: HBASE-19344-branch2.patch, HBASE-19344-branch2.patch.2.POC, wal-1-test-result.png,
wal-8-test-result.png, ycsb_result_apache20_async_wal.pdf
>
>
> The logic now is that the netty #IO thread and asyncWal's thread are the same one.
> Improvement proposal:
> 1, Split into two.
> 2, All multiWal share the netty #IO thread pool. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message