[
https://issues.apache.org/jira/browse/HBASE-15397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181455#comment-15181455
]
Hudson commented on HBASE-15397:
--------------------------------
SUCCESS: Integrated in HBase-1.4 #3 (See
[https://builds.apache.org/job/HBase-1.4/3/])
HBASE-15397 Create bulk load replication znode(hfile-refs) in ZK (tedyu: rev
42c3fcabc09fe4b05f99f78ce9aab9bdeb30932c)
*
hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationQueuesZKImpl.java
*
hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationStateZKBase.java
*
hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeersZKImpl.java
> Create bulk load replication znode(hfile-refs) in ZK replication queue by
> default
> ---------------------------------------------------------------------------------
>
> Key: HBASE-15397
> URL: https://issues.apache.org/jira/browse/HBASE-15397
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: Ashish Singhi
> Assignee: Ashish Singhi
> Fix For: 2.0.0, 1.3.0, 1.4.0
>
> Attachments: HBASE-15397.patch
>
>
> Create bulk load replication znode(hfile-refs) in ZK replication queue by
> default same as hbase replication znode.
> Otherwise the problem what happens is currently replication admin directly
> operates on ZK without routing through HM/RS. So suppose if a user enables
> the replication for bulk loaded data in server but fails to do the same in
> the client configurations then add peer will not add hfile-refs znode,
> resulting in replication failure for bulk loaded data.
> So after fixing this the behavior will be same as mutation replication.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
