[
https://issues.apache.org/jira/browse/HBASE-21365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824004#comment-16824004
]
Hudson commented on HBASE-21365:
--------------------------------
Results for branch master
[build #954 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/954/]: (x)
*{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/954//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/954//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/954//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Throw exception when user put data with skip wal to a table which may be
> replicated
> -----------------------------------------------------------------------------------
>
> Key: HBASE-21365
> URL: https://issues.apache.org/jira/browse/HBASE-21365
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Affects Versions: 3.0.0
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: HBASE-21365.master.001.patch,
> HBASE-21365.master.002.patch, HBASE-21365.master.003.patch
>
>
> A real problem in our production cluster. A user point that his table's data
> can't be replicate to the peer cluster. Then we start to debug the reason. We
> checked the replication scope, checked the replication wal entry filter, and
> check the namespace,tablecfs config. But didn't found any problem. We enabled
> the RS's debug log to find the reason. Finally, we found use use put with
> skip wal to write data. But it taked a long time... Our replication use wal
> to replicate data. So the data can't be replicated to peer cluster. I thought
> throw a exception may be better for user if the table's replication scope is
> not 0. (as 0 means not replicated).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
