Geo: cache results in issue and message count being incorrect
There is a cache on the secondary that isn't being updated when new issues are created on the primary. This causes the issue count to be unchanged despite the issue being accessible on the secondary.
We should expire/update the cache when data changes.