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

Hudson commented on HBASE-20742:
--------------------------------

Results for branch branch-2
        [build #883 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/883/]: 
(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/883//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/883//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/883//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


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


> Always create WAL directory for region server
> ---------------------------------------------
>
>                 Key: HBASE-20742
>                 URL: https://issues.apache.org/jira/browse/HBASE-20742
>             Project: HBase
>          Issue Type: Bug
>          Components: wal
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.1.0
>
>         Attachments: HBASE-20742.patch
>
>
> After HBASE-20708, when master restart, we will scan the wal directory to 
> find out the live servers. In most cases this is OK, as when we create a 
> HRegion instance at RS side, we will create a WAL for it, and the directory 
> which contains the server name will be there, even if user always use 
> SKIP_WAL.
> But there could still be problem as the directory is created in the 
> implementation of WAL, not in the initialization of region server, so if user 
> uses DisabledWALProvider then we will be in trouble.
> So let's fix it.



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

Reply via email to