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 A4B8018111 for ; Sat, 14 Nov 2015 16:06:11 +0000 (UTC) Received: (qmail 96224 invoked by uid 500); 14 Nov 2015 16:06:11 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 96152 invoked by uid 500); 14 Nov 2015 16:06:11 -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 96121 invoked by uid 99); 14 Nov 2015 16:06:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Nov 2015 16:06:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 179952C1F5D for ; Sat, 14 Nov 2015 16:06:11 +0000 (UTC) Date: Sat, 14 Nov 2015 16:06:11 +0000 (UTC) From: "Heng Chen (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-14756) Break out ClientBackoffPolicy factors into configurable and stackable components 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-14756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005452#comment-15005452 ] Heng Chen commented on HBASE-14756: ----------------------------------- Suggestions? [~apurtell] > Break out ClientBackoffPolicy factors into configurable and stackable components > -------------------------------------------------------------------------------- > > Key: HBASE-14756 > URL: https://issues.apache.org/jira/browse/HBASE-14756 > Project: HBase > Issue Type: Improvement > Reporter: Andrew Purtell > Fix For: 2.0.0, 1.3.0 > > Attachments: HBASE-14756.patch > > > Currently ExponentialClientBackoffPolicy evaluates three load parameters sent back in results from the server. The policy is fixed in implementation. Instead it should be possible to define the collection of considered load factors via configuration, and for each selected term parameterize how the load factor should contribute to the backoff calculation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)