Geo: Timeout reaching the secondary may cause the primary to display stale data
If you look at the Geo admin page from the primary on GitLab.com, you see this:
On the secondary, however, you see this:
I'm not sure why the primary is timing out after 10 s, but the secondary is not.
But we need to call out to the user that the data may be stale more prominently because I think it's easy to miss.
It has the
time-out icon after the progress bar while the data is out of date.