Page MenuHomeSoftware Heritage

Fix swh indexer journal client service
Closed, MigratedEdits Locked

Description

It's no longer running since 06/2020.

This problem is 2-fold:

  1. D4599: It's a configuration loading problem. It does not read its configuration even when provided.
  1. D4605: The current indexer journal client implementation relies on the old origin_visit model with "status" field. As this no longer exists, the code needs to be modified to subscribe to origin_visit_status instead.

Event Timeline

ardumont triaged this task as Normal priority.Nov 26 2020, 12:21 PM
ardumont created this task.

and indexer 0.6.1 is now packaged. We have everything we need to unstuck it now.

It would be nice if the tests for this journal client used an actual storage with a journal writer, rather than fully mocked topics. Doing this would have caught the original breakage.

It would be nice if the tests for this journal client used an actual storage with a journal writer, rather than fully mocked topics. Doing this would have caught the original breakage.

Agreed btw, I've opened T2821 for this.

ardumont claimed this task.
ardumont updated the task description. (Show Details)
ardumont updated the task description. (Show Details)

Deployed the following:

  • Indexer/Indexer storage 0.6.3
  • Indexer journal client unstuck
  • And Indexer workers are running again.

(grafana is tagged).