Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1841E200BFF for ; Tue, 13 Dec 2016 03:30:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1709B160B22; Tue, 13 Dec 2016 02:30:01 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5E250160B2A for ; Tue, 13 Dec 2016 03:30:00 +0100 (CET) Received: (qmail 12083 invoked by uid 500); 13 Dec 2016 02:29:59 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 11814 invoked by uid 99); 13 Dec 2016 02:29:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Dec 2016 02:29:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 2CD732C03E1 for ; Tue, 13 Dec 2016 02:29:59 +0000 (UTC) Date: Tue, 13 Dec 2016 02:29:59 +0000 (UTC) From: "binlijin (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (HBASE-15756) Pluggable RpcServer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 13 Dec 2016 02:30:01 -0000 [ https://issues.apache.org/jira/browse/HBASE-15756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743880#comment-15743880 ] binlijin edited comment on HBASE-15756 at 12/13/16 2:29 AM: ------------------------------------------------------------ The current RpcServer is complicated, it support plain data/security/encryption data... We only use plain data, do not use security/encryption. I think it need time to stabilize the Netty4RpcServer with all function and do not break the wire format. And i think make RpcServer pluggable can make it easy to implement Netty4RpcServer and switch from RpcServer to Netty4RpcServer. When Netty4RpcServer is stable than we can delete the current RpcServer. was (Author: aoxiang): The current RpcServer is complicated, it support plain data/security/encryption data... We only use plain data, do not use security/encryption. I think it need time to stabilize the Netty4RpcServer with all function and do not break the wire format. And i think make RpcServer pluggable can make it easy to implement Netty4RpcServer and switch from RpcServer to Netty4RpcServer. When Netty4RpcServer is stabile than we can delete the current RpcServer. > Pluggable RpcServer > ------------------- > > Key: HBASE-15756 > URL: https://issues.apache.org/jira/browse/HBASE-15756 > Project: HBase > Issue Type: Improvement > Components: Performance, rpc > Reporter: binlijin > Assignee: binlijin > Priority: Critical > Fix For: 2.0.0 > > Attachments: Cluster_total_QPS.png, MultiResponder.branch-1.patch, MultiResponder.master.patch, Netty4RpcServer_forperf.patch, NettyRpcServer.patch, NettyRpcServer_forperf.patch, PooledByteBufAllocator.patch, PooledByteBufAllocator2.patch, gc.png, gets.png, gets.png, idle.png, patched.vs.patched_and_cached.vs.no_patch.png, queue.png > > > Current we use a simple RpcServer, and can not configure and use other implementation.This issue is to make the RpcServer pluggable, so we can make other implementation for example netty rpc server. Patch will upload laterly -- This message was sent by Atlassian JIRA (v6.3.4#6332)