You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2017/12/01 01:30:00 UTC
[jira] [Commented] (HBASE-19344) improve asyncWAL by using
Independent thread for netty #IO in FanOutOneBlockAsyncDFSOutput
[ https://issues.apache.org/jira/browse/HBASE-19344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273797#comment-16273797 ]
Duo Zhang commented on HBASE-19344:
-----------------------------------
Let me commit.
> 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: Duo Zhang
> Fix For: 2.0.0
>
> Attachments: HBASE-19344-branch-ycsb-1.png, HBASE-19344-branch.ycsb.png, HBASE-19344-branch.ycsb.png, HBASE-19344-branch2.patch, HBASE-19344-branch2.patch.2.POC, HBASE-19344-v1.patch, HBASE-19344.patch, 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)