Skip to content

Gracefully handle case when no shard data is available

Stan Hu requested to merge sh-handle-no-shard-data-available into master

It's possible that if the GeoNodeStatus fails to fetch, we might end up with a state where the primary loads the last known state without any shard information. In this case, we should just report "UNKNOWN" for the storage configuration match check.

Relates to #4586 (closed)

Merge request reports