Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2E6AC1073C for ; Wed, 8 May 2013 13:30:05 +0000 (UTC) Received: (qmail 50952 invoked by uid 500); 8 May 2013 13:30:03 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 50468 invoked by uid 500); 8 May 2013 13:29:59 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 50441 invoked by uid 99); 8 May 2013 13:29:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 May 2013 13:29:58 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates 209.85.160.47 as permitted sender) Received: from [209.85.160.47] (HELO mail-pb0-f47.google.com) (209.85.160.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 May 2013 13:29:51 +0000 Received: by mail-pb0-f47.google.com with SMTP id uo1so1219513pbc.34 for ; Wed, 08 May 2013 06:29:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=CLZLKJ+cEGz73q+0em1aOenPlQmi06kBEK1yxy6w4Sc=; b=pNFtiwrCei7a161rO/AMDPiTsSxbH7H4uOBuEwUBZcaheUkzjVMthcKBieRNVE8XDK KB/aQj0+4mSp+9ahPX1AA+PC0iwFMea8M6Uz6gC8eNPGjHhflf8ISH9SECpcXbZXm2OV rHNtgb6D7tvg5NZxddwQAxp8weURbVe+3faUjdMFb5AEC1EM7d+lg2mVhlj9X1gWE5xF sOX79ksH6O4GTTMozulFi17D5ZarrykE0KKXMPaIg9nEs7cR4Ye9blh8cHZb6g1r/Adh 2ozE3/0aiAAcVG9VWDN/gbgIL3mqgIYyHd54GUVErpFe7DO3ORTiH46dHvWygOmFfW1c JmKA== X-Received: by 10.68.92.100 with SMTP id cl4mr7530815pbb.130.1368019770062; Wed, 08 May 2013 06:29:30 -0700 (PDT) Received: from [192.168.0.14] (c-24-130-233-55.hsd1.ca.comcast.net. [24.130.233.55]) by mx.google.com with ESMTPSA id ih1sm32599474pbb.44.2013.05.08.06.29.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 May 2013 06:29:28 -0700 (PDT) References: <1366799107669-4042838.post@n3.nabble.com> <1366935529.37434.YahooMailNeo@web140604.mail.bf1.yahoo.com> <1367996324709-4043876.post@n3.nabble.com> Mime-Version: 1.0 (1.0) In-Reply-To: <1367996324709-4043876.post@n3.nabble.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: Cc: "user@hbase.apache.org" X-Mailer: iPhone Mail (10B146) From: Ted Yu Subject: Re: HBase - prioritizing writes over reads? Date: Wed, 8 May 2013 06:29:20 -0700 To: "user@hbase.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org Can you give more details to the prioritization ? I assume you were talking about user tables.=20 Cheers On May 7, 2013, at 11:58 PM, kzurek wrote: > Thanks for the help. >=20 >=20 >=20 > -- > View this message in context: http://apache-hbase.679495.n3.nabble.com/HBa= se-prioritizing-writes-over-reads-tp4042838p4043876.html > Sent from the HBase User mailing list archive at Nabble.com.