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 33D6AE37B for ; Mon, 14 Jan 2013 21:34:15 +0000 (UTC) Received: (qmail 58517 invoked by uid 500); 14 Jan 2013 21:34:14 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 58480 invoked by uid 500); 14 Jan 2013 21:34:14 -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 58436 invoked by uid 99); 14 Jan 2013 21:34:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2013 21:34:14 +0000 Date: Mon, 14 Jan 2013 21:34:14 +0000 (UTC) From: "Elliott Clark (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-7533) Write an RPC Specification for 0.96 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553139#comment-13553139 ] Elliott Clark commented on HBASE-7533: -------------------------------------- At this point a rogue client can pretty easily bring down a cluster, so I don't think that adding the complexity of a rules based system on the server will really buy us any resiliency. We could be sanity check the priority on the server side. bq.There could be a bunch of other factors that determine the priority I don't think that we can anticipate all of the factors that users will want to include. So it's easier to let users add their logic on the client side rather than the server side. Additionally having the ability to expose priority to the user would be really useful feature that we would get for almost no extra cost. In my eyes that would be a start towards allowing users to have mapred and realtime use cases on the same hardware. > Write an RPC Specification for 0.96 > ----------------------------------- > > Key: HBASE-7533 > URL: https://issues.apache.org/jira/browse/HBASE-7533 > Project: HBase > Issue Type: Bug > Reporter: stack > Assignee: stack > Fix For: 0.96.0 > > > RPC format is changing for 0.96 to accomodate our protobufing all around. Here is a first cut. Please shred: https://docs.google.com/document/d/1-1RJMLXzYldmHgKP7M7ynK6euRpucD03fZ603DlZfGI/edit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira