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

Hudson commented on HBASE-23737:
--------------------------------

Results for branch branch-2.2
        [build #767 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/767/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/767//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/767//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/767//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> [Flakey Tests] TestFavoredNodeTableImport fails 30% of the time
> ---------------------------------------------------------------
>
>                 Key: HBASE-23737
>                 URL: https://issues.apache.org/jira/browse/HBASE-23737
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Michael Stack
>            Assignee: Michael Stack
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0, 2.1.9, 2.2.4
>
>         Attachments: 
> 0001-HBASE-23737-Flakey-Tests-TestFavoredNodeTableImport-.patch, 
> 0001-HBASE-23737-Flakey-Tests-TestFavoredNodeTableImport.addendum.fix.patch
>
>
> Spent time on TestFavoredNodeTableImport. It fails w/ an NPE when we go to 
> get favorednodes for one of the regions. It is sporadic. Fails for me locally 
> too about 30% of the time.
> I tried to study where we are going wrong. The balancer is disabled when we 
> start the cluster up again on FN balancer... but this don't seem to be the 
> problem.
> Looks like laggard Regions taking their time to open means they don't show in 
> the global list of favored nodes when the checking runs. Adding a wait till 
> no RIT seems to stabilize the test.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to