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 AFAD81016C for ; Wed, 24 Apr 2013 10:25:55 +0000 (UTC) Received: (qmail 26955 invoked by uid 500); 24 Apr 2013 10:25:53 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 26810 invoked by uid 500); 24 Apr 2013 10:25:53 -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 26794 invoked by uid 99); 24 Apr 2013 10:25:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Apr 2013 10:25:53 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=URI_HEX X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Apr 2013 10:25:48 +0000 Received: from ben.nabble.com ([192.168.236.152]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1UUwst-0002CW-Li for user@hbase.apache.org; Wed, 24 Apr 2013 03:25:07 -0700 Date: Wed, 24 Apr 2013 03:25:07 -0700 (PDT) From: kzurek To: user@hbase.apache.org Message-ID: <1366799107669-4042838.post@n3.nabble.com> Subject: HBase - prioritizing writes over reads? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Is it possible to prioritize writes over reads in HBase? I'm facing some I/O read related issues that influence my write clients and cluster in general (constantly growing store files on some RS). Due to the fact that I cannot let myself to loose/skip incoming data, I would like to guarantee that in case of extensive read I will be able to limit incoming read requests, so that write requests wont be influenced. Is it possible? If so what would be the best way to that and where it should be placed - on the client or cluster side)? -- View this message in context: http://apache-hbase.679495.n3.nabble.com/HBase-prioritizing-writes-over-reads-tp4042838.html Sent from the HBase User mailing list archive at Nabble.com.