Details
-
Improvement
-
Resolution: Fixed
-
Major
-
3.0
-
Security Level: Public
-
None
-
CBG Sprint 137
-
1
Description
Database configs store a "bucket" field - which in most cases points to the "owning" bucket of the config.
This assumption falls apart when a bucket's contents (including dbconfig) are moved to another bucket (via backup/restore or XDCR)
We should enforce the "bucket" field in the dbconfig matches on both insert (which we already do), and on load to prevent backed up/restored buckets from being used by SG unintentionally.
Need to ensure that databases and config config overwrite is allowed for already existing and mismatched configs (e.g. a backup/restored bucket can be used after an explicit update to fix the bucket field)
Attachments
Issue Links
- Clones
-
CBG-3292 Enforce "bucket" field match in DbConfig
- Closed
- relates to
-
CBG-3275 Verify behaviour of non-matching bucket field in dbconfig
- Closed
-
CBG-3430 [3.1.2 backport] Deterministic database/bucket bootstrapping
- Resolved
-
CBG-3276 Deterministic database/bucket bootstrapping
- Closed
-
CBG-3431 [3.0.9 backport] Deterministic database/bucket bootstrapping
- Closed