Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Mon, 14 Nov 2016 12:20:58 +0000 (UTC)
From: "Guanghao Zhang (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.13020494.1479126023000.268822.1479126058877@Atlassian.JIRA>
In-Reply-To: <JIRA.13020494.1479126023000@Atlassian.JIRA>
References: <JIRA.13020494.1479126023000@Atlassian.JIRA> <JIRA.13020494.1479126023352@arcas>
Subject: [jira] [Created] (HBASE-17088) Refactor
 RWQueueRpcExecutor/BalancedQueueRpcExecutor/RpcExecutor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 14 Nov 2016 12:21:00 -0000

Guanghao Zhang created HBASE-17088:
--------------------------------------

             Summary: Refactor RWQueueRpcExecutor/BalancedQueueRpcExecutor/RpcExecutor
                 Key: HBASE-17088
                 URL: https://issues.apache.org/jira/browse/HBASE-17088
             Project: HBase
          Issue Type: Improvement
          Components: rpc
    Affects Versions: 2.0.0
            Reporter: Guanghao Zhang


1. The RWQueueRpcExecutor has eight constructor method and the longest one has ten parameters. But It is only used in SimpleRpcScheduler and easy to confused when read the code.
2. There are duplicate method implement in RWQueueRpcExecutor and BalancedQueueRpcExecutor. They can be implemented in their parent class RpcExecutor.
3. SimpleRpcScheduler read many configs to new RpcExecutor. But the CALL_QUEUE_SCAN_SHARE_CONF_KEY is only needed by RWQueueRpcExecutor. And CALL_QUEUE_CODEL_TARGET_DELAY, CALL_QUEUE_CODEL_INTERVAL and CALL_QUEUE_CODEL_LIFO_THRESHOLD are only needed by AdaptiveLifoCoDelCallQueue.

So I thought we can refactor it. Suggestions are welcome.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)