Closed natefoo closed 1 year ago
@natefoo You can now set amqp_publish_timeout
in pulsar's app config, that should at a minimum fail and log an exception. Not sure if we should retry this or not, probably not ? We've also got sentry_dsn
in pulsar's app config, that should help discover errors.
Let me know if that works as it should, I would then set a default value.
The notebook has not been fetched:
Pulsar then attempts to notify Galaxy via a failure status update message:
But that message is never received (and as far as I can tell, silently never published).
For the record, the underlying problem appears to be with name resolution in the k8s cluster: