[
https://issues.apache.org/jira/browse/HBASE-19344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265950#comment-16265950
]
Duo Zhang commented on HBASE-19344:
-----------------------------------
Talked with [~chancelq] offline and we have done more tests. Seems the reason
is not sharing event loop with others, but we only use one thread for every
thing in AsyncFSWAL and AsyncDFSOutput so the thread is over loaded.
He will put all the tests results later since he losses the connection to the
world out of China temporarily...
For me, I will start working on implementing the new logic described in the
POC. As said above it is not straight-forward for fail recovery.
Thanks.
> 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)
