[
https://issues.apache.org/jira/browse/HBASE-20624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488956#comment-16488956
]
Hudson commented on HBASE-20624:
--------------------------------
Results for branch master
[build #343 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/343/]: (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/master/343//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/master/343//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/master/343//JDK8_Nightly_Build_Report_(Hadoop3)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
> Race in ReplicationSource which causes walEntryFilter being null when
> creating new shipper
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-20624
> URL: https://issues.apache.org/jira/browse/HBASE-20624
> Project: HBase
> Issue Type: Bug
> Components: Replication
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-20624.patch
>
>
> We initialize the ReplicationSource in a background thread to avoid blocking
> the peer modification. And when enqueueLog is called and we want to start a
> new shipper, we will check whether the replicationEndpoint is initialized, if
> so, we will start a new shipper. But in the initialize thread, we will
> initialize walEntryFilter after replicationEndpoint , so it is possible that
> when we start a new shipper, the walEntryFilter is still null and cause NPE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
