Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 11 Oct 2015 05:01:05 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12896012.1443077533000.8460.1444539665743@Atlassian.JIRA>
In-Reply-To: <JIRA.12896012.1443077533000@Atlassian.JIRA>
References: <JIRA.12896012.1443077533000@Atlassian.JIRA>
 <JIRA.12896012.1443077533604@arcas>
Subject: [jira] [Commented] (HBASE-14479) Apply the Leader/Followers pattern
 to RpcServer's Reader
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-14479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952159#comment-14952159 ] 

stack commented on HBASE-14479:
-------------------------------

[~nkeywal] FYI. You'll like this one.

[~ikeda] Should we use this patten elsewhere, say, in the handoff to syncer threads in WAL? See http://hbase.apache.org/xref/org/apache/hadoop/hbase/regionserver/wal/FSHLog.html#1770

if I understand the pattern right, we could purge Readers and have Handlers themselves do the select read from the socket (one less handoff)?


> Apply the Leader/Followers pattern to RpcServer's Reader
> --------------------------------------------------------
>
>                 Key: HBASE-14479
>                 URL: https://issues.apache.org/jira/browse/HBASE-14479
>             Project: HBase
>          Issue Type: Improvement
>          Components: IPC/RPC, Performance
>            Reporter: Hiroshi Ikeda
>            Assignee: Hiroshi Ikeda
>            Priority: Minor
>         Attachments: HBASE-14479-V2 (1).patch, HBASE-14479-V2.patch, HBASE-14479-V2.patch, HBASE-14479.patch, gc.png, gets.png, io.png, median.png
>
>
> {{RpcServer}} uses multiple selectors to read data for load distribution, but the distribution is just done by round-robin. It is uncertain, especially for long run, whether load is equally divided and resources are used without being wasted.
> Moreover, multiple selectors may cause excessive context switches which give priority to low latency (while we just add the requests to queues), and it is possible to reduce throughput of the whole server.


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