[
https://issues.apache.org/jira/browse/HBASE-24736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206105#comment-17206105
]
Nicholas Jiang commented on HBASE-24736:
----------------------------------------
[~zghao], IMO, the second choice that set watcher on znode and read the WAL
when ReplicationQueueStorage send WAL event to ZK makes sense and is more
flexible. If you agree with the second choice, I would like to set watcher on
znode to listen to WAL events. What do you think about and which choice do you
prefer?
> Remove ReplicationSourceInterface#enqueueLog method and get the new WAL to
> replicate from ReplicationQueueStorage directly
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-24736
> URL: https://issues.apache.org/jira/browse/HBASE-24736
> Project: HBase
> Issue Type: Sub-task
> Reporter: Guanghao Zhang
> Priority: Major
>
> There are two choices for this now.
> # Start a backgroud thread and keep to read the new WAL from
> ReplicationQueueStorage.
> # The default ReplicationQueueStorage is based on ZK. Set watcher on znode
> and read the WAL when there are zk event.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
