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 E5CC4200D35 for ; Tue, 24 Oct 2017 07:40:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E472B160BF0; Tue, 24 Oct 2017 05:40:07 +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 351DD1609E0 for ; Tue, 24 Oct 2017 07:40:07 +0200 (CEST) Received: (qmail 69289 invoked by uid 500); 24 Oct 2017 05:40:06 -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 69275 invoked by uid 99); 24 Oct 2017 05:40:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Oct 2017 05:40:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 5DFF21805BF for ; Tue, 24 Oct 2017 05:40:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -96.202 X-Spam-Level: X-Spam-Status: No, score=-96.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_TIME=3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 88aMLOxGxIow for ; Tue, 24 Oct 2017 05:40:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 3B31E5FC1C for ; Tue, 24 Oct 2017 05:40:04 +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 5BB22E041C for ; Tue, 24 Oct 2017 05:40:02 +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 B948321EE3 for ; Tue, 24 Oct 2017 05:40:00 +0000 (UTC) Date: Tue, 24 Oct 2017 05:40:00 +0000 (UTC) From: "ramkrishna.s.vasudevan (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18946) Stochastic load balancer assigns replica regions to the same RS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 24 Oct 2017 05:40:08 -0000 [ https://issues.apache.org/jira/browse/HBASE-18946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216347#comment-16216347 ] ramkrishna.s.vasudevan commented on HBASE-18946: ------------------------------------------------ [~saint.ack@gmail.com] Thanks for the comment. Yes in a way I agree that fixing it in Balancer is best. But still in these cases the bulking mechanism is not a logical bulking instead it depends on the timed wait and the size of the queue. So the balancer may not really know what has been balanced by the time the next bulked set of region comes in. Any suggestions? I can still check if it is possible to make balancer aware of this. But this mechanism solves some more issues in other related areas since we know the set of regions to be balanced at one shot. > Stochastic load balancer assigns replica regions to the same RS > --------------------------------------------------------------- > > Key: HBASE-18946 > URL: https://issues.apache.org/jira/browse/HBASE-18946 > Project: HBase > Issue Type: Bug > Affects Versions: 2.0.0-alpha-3 > Reporter: ramkrishna.s.vasudevan > Assignee: ramkrishna.s.vasudevan > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18946.patch, HBASE-18946.patch, TestRegionReplicasWithRestartScenarios.java > > > Trying out region replica and its assignment I can see that some times the default LB Stocahstic load balancer assigns replica regions to the same RS. This happens when we have 3 RS checked in and we have a table with 3 replicas. When a RS goes down then the replicas being assigned to same RS is acceptable but the case when we have enough RS to assign this behaviour is undesirable and does not solve the purpose of replicas. > [~huaxiang] and [~enis]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)