It looks like Prefect swallows errors when using BatchSubmit. I am getting a generic "FAIL signal raised: FAIL("Failed to submit job 'blah' to AWS Batch.")" error. This makes it hard to debug since this flow runs fine locally but is failing on my ECSRunner. Can you log the stack trace or error message from boto3?
although there may be concerns about sending that data to Prefect.
t
Trevor Kramer
03/08/2021, 8:05 PM
I set PREFECT__LOGGING__EXTRA_LOGGERS="['boto3']" env in the Job definition of my ECSRunner but I'm still not seeing any boto3 logs. Does this need to be set on the agent as well?
Trevor Kramer
03/09/2021, 10:04 PM
Any tips on how to debug this?
z
Zanie
03/09/2021, 10:07 PM
Personally, I'd copy the BatchSubmit task locally and just add the
self.logger
call that I outlined above to get the answer ASAP. I've also sent a message to the rest of the team asking if anything is missing as far as getting boto logs to show up.
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.