[
https://issues.apache.org/jira/browse/HBASE-20856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-20856:
--------------------------
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.
was:
With this change if WAL's meta provider (hbase.wal.meta_provider) is not
explicitly set, it uses whatever set with the default for WAL's provider
(hbase.wal.provider).
This improvement avoids a use case of unexpectedly using two different WAL
providers when only WAL's meta provider is set to non-default but not WAL's
provider.
This change is operational incompatible with previous HBase version because the
default of WAL's meta provider is no longer always default to
AsyncFSWALProvider.
> PITA having to set WAL provider in two places
> ---------------------------------------------
>
> Key: HBASE-20856
> URL: https://issues.apache.org/jira/browse/HBASE-20856
> Project: HBase
> Issue Type: Improvement
> Components: Operability, wal
> Affects Versions: 3.0.0
> Reporter: stack
> Assignee: Tak Lon (Stephen) Wu
> Priority: Minor
> Fix For: 3.0.0, 2.0.2, 2.2.0, 2.1.1
>
> Attachments: HBASE-20856.master.001.patch,
> HBASE-20856.master.002.patch, HBASE-20856.master.003.patch
>
>
> Courtesy of [~elserj], 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
