Page MenuHomePhabricator

wdqs replication lagging behind on some nodes
Closed, DuplicatePublic

Description

In the last few days, we've have 3 instances of wdqs-updater lagging behind on some nodes (but not all). It looks like replication stopped for some time and then restarted and took some time to catch up.

The fact that not all nodes stopped at the same time indicates that the problem is internal to wdqs.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

This may be related to timeout bump. Let's watch it for a while and see, maybe 1 min is too much.