Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 13 Feb 2011 07:26:57 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <924969073.13366.1297582017967.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1567433163.9266.1297381377421.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (HBASE-3523) Rewrite our client
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell commented on HBASE-3523:
---------------------------------------

bq. Are not executors thread pools?

I meant merely no creation of internal thread pools. So users can create executors with their own thread factories, etc.


> Rewrite our client
> ------------------
>
>                 Key: HBASE-3523
>                 URL: https://issues.apache.org/jira/browse/HBASE-3523
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: stack
>
> Is it just me or do others sense that there is pressure building to redo the client?  If just me, ignore the below... I'll just keep notes in here.  Otherwise, what would the requirements for a client rewrite look like?
> + Let out InterruptedException
> + Enveloping of messages or space for metadata that can be passed by client to server and by server to client; e.g. the region a.b.c moved to server x.y.z. or scanner is finished or timeout
> + A different RPC? One with tighter serialization.
> + More sane timeout/retry policy.
> Does it have to support async communication?  Do callbacks?
> What else?

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira