-
-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
freeze AWS glue job #193
Comments
... and in both cases logs were successfully and fully sent to CloudWatch by WatchTower |
I found workaround - if I add that in the end of glue job
it finishes normally |
Can you provide the code you used and maybe the version of cloudwatch? I can't get it to run via glue properly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use WatchTower as workaround for inability to change CloudWatch group for glue jobs written in Python.
But when I add WatchTower handler the glue jobs after successfuly finishing job freeze.
In Spark worker logs I see nothing - just normal finishing and after that final message that the worker had been killed by driver.
In Spark Driver I see repeated attempts to send stdout to CloudWatch by internal AWS mechanism - do not see how is possibly connected with WatchTower:
INFO LogPusher: uploading /tmp/spark-event-logs/ to s3://****
INFO MultipartUploadOutputStream: close closed:false s3://***.inprogress
If I set use_queues=False it finishes normally and in logs I see
INFO MultipartUploadOutputStream: close closed:false s3://***/FilteredOut/run-1705485647329-part-r-00002.gz
The text was updated successfully, but these errors were encountered: