[ https://issues.apache.org/jira/browse/HBASE-18946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16212288#comment-16212288 ]
ramkrishna.s.vasudevan commented on HBASE-18946: ------------------------------------------------ bq. As with some of regions with known location, there are new ones which needs to be assigned, these new ones could be assigned to the same region server which hosts the primary or other replica region. Yes agree with you. So i need to fix the issue with EnableTableHandler first. bq.The previous logic is that when the first region is queued, it starts to wait assignDispatchWaitMillis to start the real work. With the patch, the whole batch is added at once, it skipped the addFirstOne logic. Will read and understand your comment and will be back here. > 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)