You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if the database has some more/fewer fields than the latest TenantConf definition, consistency check will consider all existing shards to be in an inconsistent state.
The text was updated successfully, but these errors were encountered:
…0422)
## Problem
We were comparing serialized configs from the database with serialized
configs from memory. If fields have been added/removed to TenantConfig,
this generates spurious consistency errors. This is fine in test
environments, but limits the usefulness of this debug API in the field.
Closes: #10369
## Summary of changes
- Do a decode/encode cycle on the config before comparing it, so that it
will have exactly the expected fields.
Currently if the database has some more/fewer fields than the latest TenantConf definition, consistency check will consider all existing shards to be in an inconsistent state.
The text was updated successfully, but these errors were encountered: