Staging instance, all changes can be removed at any time

extrinsic metadata indexer complains about replication lag on a primary database

One of the extrinsic metadata indexers in production is complaining about replication lag, while it's running on the main database.

"ValueError: Unknown origin swh:1:ori:704a0188ae1baf38deca2f5680969edf90f0e0b2 for metadata target: swh:1:ori:704a0188ae1baf38deca2f5680969edf90f0e0b2. Is the swh-storage database replication lag over 60s?"

I'm not sure where the "60s" comes from, but I think this kind of issue should be reported as a warning and skipped, rather than just crashing the journal client (and blocking any further indexation).