[
https://issues.apache.org/jira/browse/HBASE-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liyin Tang updated HBASE-6103:
------------------------------
Description:
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.
was:
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 HBaseServer shall serialize the data for each connection in
parallel.
BTW, it is also one of the reasons that the parallel scanning from multiple
clients is far slower than single client case.
Summary: Optimize the HBaseServer to deserialize the data for each ipc
connection in parallel (was: HBaseServer shall serialize the data for each
connection in parallel)
> 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
> Reporter: Liyin Tang
> Assignee: Liyin Tang
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
