Replay traffic to correct an out-of-sync search index
If the data in the search index is out-of-sync with the Publishing API,
(for example, after restoring a backup), then any
unpublish messages that have not been processed need to be resent.
Content in the
govuk index is populated from the Publishing API message queue.
Missing documents can be recovered by resending the content to the message queue. In the
Publishing API, run the following rake task (including the quotes) to replay traffic between
bundle exec rake 'represent_downstream:published_between[2018-12-17T01:02:30, 2018-12-18T10:20:30]'
Other replay options are available, for example replaying all traffic for a single publishing app or doctype. Be aware that these options will replay the entire Publisher API history for that app or doctype, and may take some time.
This will not be neccessary after whitehall content has been moved to the
These indexes are populated by whitehall calling an HTTP API in Search API. Missing documents can be recovered by resending the content to Search API directly. In Whitehall, run the following rake task (including the quotes) to replay traffic between two datestamps:
bundle exec rake 'search:index:published_between[2018-12-17T01:02:30, 2018-12-18T10:20:30]'
This index is used for best bets, which are published by Search Admin
communicating with Search API directly (like how whitehall updates the
detailed indices directly). In Search Admin, run
the following rake task to resend all bets to Search API:
bundle exec rake reindex_best_bets