[HBASE-21365] Throw exception when user put data with skip wal to a table which may be replicated

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-1
• Fix Version/s: 3.0.0-alpha-1
• Component/s: Client
• Hadoop Flags: Incompatible change

Release Note

If a table's column family's replication scope is not REPLICATION_SCOPE_LOCAL, this table may be replicated to peer cluster. As hbase's replication rely on WAL, if put data with Durability.SKIP_WAL to this table, the regionserver will throw a new InvalidMutationDurabilityException to client.

• Assignee: Guanghao Zhang
• Reporter: Guanghao Zhang
• Created: 23/Oct/18 09:32
• Updated: 23/Apr/19 11:51
• Resolved: 26/Oct/18 09:56

Description

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).

Issue Links

• links to: Review Board (master)