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 3963E200C17 for ; Fri, 10 Feb 2017 18:57:48 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3629B160B5C; Fri, 10 Feb 2017 17:57:48 +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 7F9C8160B4E for ; Fri, 10 Feb 2017 18:57:47 +0100 (CET) Received: (qmail 46894 invoked by uid 500); 10 Feb 2017 17:57:46 -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 46883 invoked by uid 99); 10 Feb 2017 17:57:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2017 17:57:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 3EA58C05D7 for ; Fri, 10 Feb 2017 17:57:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id y8Y66XGeK0Fo for ; Fri, 10 Feb 2017 17:57:45 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 06B345FABF for ; Fri, 10 Feb 2017 17:57:45 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 46A30E0627 for ; Fri, 10 Feb 2017 17:57:43 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id EE96621D76 for ; Fri, 10 Feb 2017 17:57:41 +0000 (UTC) Date: Fri, 10 Feb 2017 17:57:41 +0000 (UTC) From: "Jimmy Xiang (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-17625) Slow to enable a table MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 10 Feb 2017 17:57:48 -0000 [ https://issues.apache.org/jira/browse/HBASE-17625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-17625: -------------------------------- Description: Tried to enable a table with 10k+ regions, it takes more time to generate the plan than do the actual assignment. This is so embarrassing. :) It turns out that it took quite some time to get the top HDFS block locations in registering regions when creating the Cluster object. was: Tried to enable a table with 10k+ regions, it takes more time to generate the plan than do the actual assignment. This is so embarrassing. :) It turns out that it took quite some time to get the top HDFS block locations in registering regions when creating the Cluster object. There is no new region server, why do we need such info when trying to retain assignment? Is the region availability thing related to region replica? Can we avoid such penalty if region replica in not needed? > Slow to enable a table > ---------------------- > > Key: HBASE-17625 > URL: https://issues.apache.org/jira/browse/HBASE-17625 > Project: HBase > Issue Type: Improvement > Reporter: Jimmy Xiang > > Tried to enable a table with 10k+ regions, it takes more time to generate the plan than do the actual assignment. This is so embarrassing. :) > It turns out that it took quite some time to get the top HDFS block locations in registering regions when creating the Cluster object. -- This message was sent by Atlassian JIRA (v6.3.15#6346)