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 6D192DDE0 for ; Fri, 7 Dec 2012 15:31:23 +0000 (UTC) Received: (qmail 13466 invoked by uid 500); 7 Dec 2012 15:31:23 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 13390 invoked by uid 500); 7 Dec 2012 15:31:22 -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 13380 invoked by uid 99); 7 Dec 2012 15:31:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Dec 2012 15:31:22 +0000 Date: Fri, 7 Dec 2012 15:31:22 +0000 (UTC) From: "nkeywal (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-7271) Have a single executor for all zkWorkers in the assignment manager 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-7271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nkeywal updated HBASE-7271: --------------------------- Status: Patch Available (was: Open) > Have a single executor for all zkWorkers in the assignment manager > ------------------------------------------------------------------ > > Key: HBASE-7271 > URL: https://issues.apache.org/jira/browse/HBASE-7271 > Project: HBase > Issue Type: Bug > Components: master, Region Assignment > Affects Versions: 0.96.0 > Reporter: nkeywal > Assignee: nkeywal > Fix For: 0.96.0 > > Attachments: 7271.v1.patch, 7271.v2.patch, 7271.v2.patch, 7271.v3.patch > > > The current strategy is to have an array of monothreaded executor, and hash the zk path to ensure that there are no two events on the same region executed in parallel > I think a single executor, as presented in the attached patch, is better because: > - we're guaranteed to use all threads at any time > - if managing one of the event takes longer that expected, the slowness is limited to this region, and not to all regions that have the same hashed/moduloed code > - For the nodeChildrenChanged, there is no need to choose randomly one of the worker (or, once again, the risk to get stuck if one of the event takes time to be managed). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira