[jira] [Issue Comment Deleted] (HBASE-20624) Race in ReplicationSource which causes walEntryFilter being null when creating new shipper

["Gavin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-20624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin updated HBASE-20624:
--------------------------
    Comment: was deleted

(was: A comment with security level 'jira-users' was removed.)

> 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)