hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhihong Yu (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5201) Utilize TThreadedSelectorServer and remove redundant code in ThriftServer and HRegionThriftServer
Date Tue, 17 Jan 2012 17:58:43 GMT

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

Zhihong Yu updated HBASE-5201:
------------------------------

    Release Note: 
New config parameters:

"hbase.thrift.selector.threads"  Number of selector threads for reading and writing socket
"hbase.thrift.worker.threads"  Number of threads for processing the thrift calls
"hbase.thrift.stop.timeout.seconds"  Time to wait for server to stop gracefully
"hbase.thrift.accept.queue.size.per.selector"  Maximum number of accepted elements per selector

Integrated to TRUNK.

Thanks for the patch Scott
                
> Utilize TThreadedSelectorServer and remove redundant code in ThriftServer and HRegionThriftServer
> -------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5201
>                 URL: https://issues.apache.org/jira/browse/HBASE-5201
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Scott Chen
>            Assignee: Scott Chen
>             Fix For: 0.94.0
>
>         Attachments: HBASE-5201-v2.txt, HBASE-5201-v3.txt, HBASE-5201-v4.txt, HBASE-5201.txt
>
>
> TThreadedSelectorServer is good for RPC-heavy situation because IO are not limited to
one CPU. See
> https://issues.apache.org/jira/browse/Thrift-1167
> I am porting the related classes form thrift trunk (it is not there in thrift-0.7.0).
> There are lots of repeat codes in ThriftServer and HRegionThriftServer.
> These codes are now moved to a Runnable called ThriftServerRunner.

--
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

        

Mime
View raw message