Repository navigation
extractor will never run #21
Description
if the resource or the host is not correctly computed, the extractor will never start, but also not ack the messages, resulting in the extractor being stuck.
See the following places:
pyclowder/pyclowder/connectors.py
Line 381 in b852c63
pyclowder/pyclowder/connectors.py
Line 389 in b852c63
In this case all we can do is move the message to the error queue and ack it. It is not possible to send an update to clowder.
Metadata
Metadata
Assignees
Labels
No labels
Activity
max-zilla commentedon Oct 7, 2020
Started an implementation of this here:
https://github.com/clowder-framework/pyclowder/compare/fail-gracefully-on-bad-resources
Haven't tested it yet but tried to make it generically adaptable for other connectors as well.
robkooper commentedon Oct 7, 2020
@max-zilla looks good sofar, next comes testing.