hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-6103) Optimize the HBaseServer to deserialize the data for each ipc connection in parallel
Date Sun, 05 Jun 2016 19:46:59 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-6103.
--------------------------
    Resolution: Not A Problem

Resolving as  not a problem any more. The basic idea was done in HBASE-2941 . HBASE-15967
then does the sizing by CPU count that was superior in this issue over HBASE-2941.

> Optimize the HBaseServer to deserialize the data for each ipc connection in parallel
> ------------------------------------------------------------------------------------
>
>                 Key: HBASE-6103
>                 URL: https://issues.apache.org/jira/browse/HBASE-6103
>             Project: HBase
>          Issue Type: Improvement
>          Components: Performance
>            Reporter: Liyin Tang
>            Assignee: Liyin Tang
>         Attachments: HBASE-6103-fb-89.patch
>
>
> Currently HBaseServer is running with a single listener thread, which is responsible
for accepting the connection, reading the data from network channel, deserializing the data
into writable objects and handover to the IPC handler threads. 
> When there are multiple hbase clients connecting to the region server (HBaseServer) and
reading/writing a large set of data, the listener and the respond thread will be performance
bottleneck. 
> So the solution is to deserialize the data for each ipc connection in parallel for HBaseServer
> BTW, it is also one of the reasons that the parallel scanning from multiple clients is
far slower than single client case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message