Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 44546200BBF for ; Mon, 14 Nov 2016 10:57:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 42F0B160B05; Mon, 14 Nov 2016 09:57:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 93822160B06 for ; Mon, 14 Nov 2016 10:56:59 +0100 (CET) Received: (qmail 2279 invoked by uid 500); 14 Nov 2016 09:56:58 -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 2167 invoked by uid 99); 14 Nov 2016 09:56:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Nov 2016 09:56:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7C8AD2C4C75 for ; Mon, 14 Nov 2016 09:56:58 +0000 (UTC) Date: Mon, 14 Nov 2016 09:56:58 +0000 (UTC) From: "Yu Li (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-17083) Enable hedged reads by default in hbase-2.0.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 14 Nov 2016 09:57:00 -0000 [ https://issues.apache.org/jira/browse/HBASE-17083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663335#comment-15663335 ] Yu Li commented on HBASE-17083: ------------------------------- The idea of hedge read is good but one thing to notice is the network usage. Previously with 1Gb bandwidth and hedge read enabled in our production environment we ever observed network congestion and disabled the feature afterwards, and we never tried with 10Gb bandwidth yet. Another thing to watch out is the hedge read thread pool size. IIRC, we at least need to set the pool size to {{hbase.regionserver.handler.count}} or else it might be a bottleneck point. Hope these information helps for your testing sir [~stack], and hopefully we could get some good default settings through carefully testing and assure good document supplied to users in our ref guide. > Enable hedged reads by default in hbase-2.0.0 > --------------------------------------------- > > Key: HBASE-17083 > URL: https://issues.apache.org/jira/browse/HBASE-17083 > Project: HBase > Issue Type: Improvement > Affects Versions: 2.0.0 > Reporter: stack > Assignee: stack > Priority: Critical > Fix For: 2.0.0 > > > Hedged reads came in in hadoop-2.4. hbase-2.0.0 requires a later version so we can expect support to be preseent. This issue is about a bit of testing to show defined benefit when hedged reads are on and then enabling them by default in hbase-2.0.0. > See http://hbase.apache.org/book.html#_hedged_reads for current state of the doc. > This issue came up in conversation a few of us were having Thursday and then Lars George started asking me their state in the last 24 hours. > Assigning myself to do the bit of testing and enabling. -- This message was sent by Atlassian JIRA (v6.3.4#6332)