[HBASE-20856] PITA having to set WAL provider in two places

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-1
• Fix Version/s: 3.0.0-alpha-1, 2.2.0, 2.1.1, 2.0.2
• Component/s: Operability, wal

Release Note

With this change if a WAL's meta provider (hbase.wal.meta_provider) is not explicitly set, it now defaults to whatever hbase.wal.provider is set to. Previous, the two settings operated independently, each with its own default.

This change is operationally incompatible with previous HBase versions because the default WAL meta provider no longer defaults to AsyncFSWALProvider but to hbase.wal.provider.

The thought is that this is more in line with an operator's expectation, that a change in hbase.wal.provider is sufficient to change how WALs are written, especially given hbase.wal.meta_provider is an obscure configuration and that the very idea that meta regions would have their own wal provider would likely come as a surprise.

• Assignee: Tak-Lon (Stephen) Wu
• Reporter: Michael Stack
• Created: 06/Jul/18 16:02
• Updated: 07/Feb/19 00:53
• Resolved: 01/Aug/18 22:01

Description

Courtesy of Josh Elser, I learn that changing WAL we need to set two places... both hbase.wal.meta_provider and hbase.wal.provider. Operator should only have to set it in one place; hbase.wal.meta_provider should pick up general setting unless hbase.wal.meta_provider is explicitly set.

Issue Links

• breaks: HBASE-21843 RegionGroupingProvider breaks the meta wal file name pattern which may cause data loss for meta region
• breaks: HBASE-21247 Custom Meta WAL Provider doesn't default to custom WAL Provider whose configuration value is outside the enums in Providers
• links to: PR#88 for porting to branch-2
• links to: pull request #83