[
https://issues.apache.org/jira/browse/HBASE-19904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347869#comment-16347869
]
Duo Zhang commented on HBASE-19904:
-----------------------------------
{quote}
At system level, there's very clear strong dependency of replication on wal,
there's no way we should make wal depend on replication.
{quote}
No. At least, before I introduce WALFileLengthProvider, replication does not
depend on WAL, they just communicate with the HDFS. And after synchronous
replication, there will be strong dependency of WAL on replication, since it
needs to know whether we should write to the remote HDFS, so we must initialize
Replication before WAL.
So my solution is simple, revert back to the old implementation, initialize
Replication first, and then WAL. It is easy to understand.
Thanks.
> Find a better way to deal with the cyclic dependency when initializing WAL
> and Replication
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-19904
> URL: https://issues.apache.org/jira/browse/HBASE-19904
> Project: HBase
> Issue Type: Improvement
> Components: Replication, wal
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.0.0-beta-2
>
> Attachments: HBASE-19904.patch
>
>
> When implementing synchronous replication, I found that we need to depend
> more on replication in WAL so it is even more pain...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
