[ 
https://issues.apache.org/jira/browse/HBASE-21102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16614372#comment-16614372
 ] 

ramkrishna.s.vasudevan commented on HBASE-21102:
------------------------------------------------

[~Apache9]
I already downloaded the artificats from the build and verified the logs. The 
existing logs does not give much info. When I wanted to fix the flakiness 
before I committed the patch I added intermediatory logs and only then found 
that the randomAssignment() was having some issues. Since in my local cluster 
the test passes consistently I would like to push in some Logs and then rerun 
the tests. Probably in precommits. If pre-commit does not fail then let me push 
those logs and then generate a build. But one question I have is will the 
flakey test re run after the commit with Log msgs added is done?

> ServerCrashProcedure should select target server where no other replicas 
> exist for the current region
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-21102
>                 URL: https://issues.apache.org/jira/browse/HBASE-21102
>             Project: HBase
>          Issue Type: Bug
>          Components: Region Assignment
>    Affects Versions: 3.0.0, 2.2.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Major
>         Attachments: HBASE-21102_1.patch, HBASE-21102_2.patch, 
> HBASE-21102_3.patch, HBASE-21102_4.patch, HBASE-21102_initial.patch
>
>
> Currently when a server with region replica crashes, when the target server 
> is created for the replica region assignment there is no guarentee that a 
> server is selected where there is no other replica for the current region 
> getting assigned. It so happens that currently we do an assignment randomly 
> and later the LB comes and identifies these cases and again does MOVE for 
> such regions. It will be better if we can identify target servers at least 
> minimally ensuring that replicas are not colocated.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to