Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
-
Description
Currently we plan to use HBase Replication feature to deal with disaster tolerance scenario.But we encounter an issue that we will use bulkload very frequently,because bulkload bypass write path, and will not generate WAL, so the data will not be replicated to backup cluster. It's inappropriate to bukload twice both on active cluster and backup cluster. So i advise do some modification to bulkload feature to enable bukload to both active cluster and backup cluster
Attachments
Attachments
Issue Links
- blocks
-
HBASE-14937 Make rpc call timeout for replication adaptive
- Closed
- breaks
-
HBASE-15578 Handle HBASE-15234 for ReplicationHFileCleaner
- Closed
- incorporates
-
HBASE-14938 Limit the number of znodes for ZK in bulk loaded hfile replication
- Closed
- is related to
-
HBASE-22380 break circle replication when doing bulkload
- Closed
- relates to
-
HBASE-15397 Create bulk load replication znode(hfile-refs) in ZK replication queue by default
- Closed
-
HBASE-15425 Failing to write bulk load event marker in the WAL is ignored
- Closed
-
HBASE-15669 HFile size is not considered correctly in a replication request
- Closed
-
HBASE-15952 Bulk load data replication is not working when RS user does not have permission on hfile-refs node
- Closed
-
HBASE-17290 Potential loss of data for replication of bulk loaded hfiles
- Closed
-
HBASE-15424 Add bulk load hfile-refs for replication in ZK after the event is appended in the WAL
- Closed
-
HBASE-15668 HFileReplicator$Copier fails to replicate other hfiles in the request when a hfile in not found in FS anywhere
- Closed
-
HBASE-14945 Backport HBASE-13153 (Bulk loaded HFile replication) to 0.98
- Closed
-
HBASE-14939 Document bulk loaded hfile replication
- Closed
-
HBASE-15888 Extend HBASE-12769 for bulk load data replication
- Closed
- links to