Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F0C96107BD for ; Fri, 16 Jan 2015 13:14:33 +0000 (UTC) Received: (qmail 36392 invoked by uid 500); 16 Jan 2015 13:14:35 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 36344 invoked by uid 500); 16 Jan 2015 13:14:35 -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 36332 invoked by uid 99); 16 Jan 2015 13:14:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Jan 2015 13:14:35 +0000 Date: Fri, 16 Jan 2015 13:14:35 +0000 (UTC) From: "Jurriaan Mous (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-12684) Add new AsyncRpcClient MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-12684?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Jurriaan Mous updated HBASE-12684: ---------------------------------- Attachment: HBASE-12684-v31.patch Epoll indeed seems to be a cause of the unstable test runs. So I turned it = off again in latest patch. Is it ok to commit without Epoll enabled by default? > Add new AsyncRpcClient > ---------------------- > > Key: HBASE-12684 > URL: https://issues.apache.org/jira/browse/HBASE-12684 > Project: HBase > Issue Type: Improvement > Components: Client > Reporter: Jurriaan Mous > Assignee: Jurriaan Mous > Attachments: HBASE-12684-DEBUG2.patch, HBASE-12684-DEBUG3.patch, = HBASE-12684-v1.patch, HBASE-12684-v10.patch, HBASE-12684-v11.patch, HBASE-1= 2684-v12.patch, HBASE-12684-v13.patch, HBASE-12684-v14.patch, HBASE-12684-v= 15.patch, HBASE-12684-v16.patch, HBASE-12684-v17.patch, HBASE-12684-v17.pat= ch, HBASE-12684-v18.patch, HBASE-12684-v19.1.patch, HBASE-12684-v19.patch, = HBASE-12684-v19.patch, HBASE-12684-v2.patch, HBASE-12684-v20-heapBuffer.pat= ch, HBASE-12684-v20.patch, HBASE-12684-v21-heapBuffer.1.patch, HBASE-12684-= v21-heapBuffer.patch, HBASE-12684-v21.patch, HBASE-12684-v22.patch, HBASE-1= 2684-v23-epoll.patch, HBASE-12684-v24.patch, HBASE-12684-v24.patch, HBASE-1= 2684-v24.patch, HBASE-12684-v24.patch, HBASE-12684-v24.patch, HBASE-12684-v= 25.patch, HBASE-12684-v26.patch, HBASE-12684-v27.patch, HBASE-12684-v27.pat= ch, HBASE-12684-v28.patch, HBASE-12684-v29.patch, HBASE-12684-v3.patch, HBA= SE-12684-v30.patch, HBASE-12684-v30.patch, HBASE-12684-v30.patch, HBASE-126= 84-v31.patch, HBASE-12684-v4.patch, HBASE-12684-v5.patch, HBASE-12684-v6.pa= tch, HBASE-12684-v7.patch, HBASE-12684-v8.patch, HBASE-12684-v9.patch, HBAS= E-12684.patch, Screen Shot 2015-01-11 at 11.55.32 PM.png, myrecording.jfr, = q.png, requests.png > > > With the changes in HBASE-12597 it is possible to add new RpcClients. Thi= s issue is about adding a new Async RpcClient which would enable HBase to d= o non blocking protobuf service communication. > Besides delivering a new AsyncRpcClient I would also like to ask the ques= tion what it would take to replace the current RpcClient? This would enable= to simplify async code in some next issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)