You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2018/10/23 09:33:00 UTC
[jira] [Created] (HBASE-21365) Throw exception when user put data
with skip wal to a table which may be replicated
Guanghao Zhang created HBASE-21365:
--------------------------------------
Summary: 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
Reporter: Guanghao Zhang
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)