Skip to content

Geo: Use database-cached status if redis-cached status is unavailable

Nick Thomas requested to merge (removed):status-on-secondary into master

What does this MR do?

Falls back to database-held values for Geo node status if the redis-held values are not present, in case they're present.

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

It addresses an inconsistency between the primary and secondary where a secondary's status is in the database, but the secondary is having trouble generating something and its redis cache is empty. Seen on staging.gitlab.com today.

Screenshots (if relevant)

Fixes this situation:

Screenshot_from_2018-08-09_12-09-39

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Edited by Nick Thomas

Merge request reports

Loading