- 最新
- 投票最多
- 评论最多
Hi,
I understand that you are facing the “ConnectionRefusedError” while running your glue job. This can happen because of multiple reasons.
-
If you are using any glue connection in your job then please ensure that the “test connection” is successful.
-
Please check the CloudWatch Logs to see if there is any specific error other than the “ConnectionRefusedError”.
-
If you are observing the "Max number of executor failures reached" error or any errors that shows that this could be a memory issue then please make sure you are using the “G.2X” worker type as this is the largest worker type available for Glue ETL jobs. If you still face the memory issues even after this then you would need to look further into optimising the glue script. Please refer to the following documentation for more details on the same -
https://aws.amazon.com/blogs/big-data/optimize-memory-management-in-aws-glue/
-
If the issue still persist, then please open a support case with AWS Glue providing the connection details along with the Job Run Id and Region - https://docs.aws.amazon.com/awssupport/latest/user/case-management.html#creating-a-support-case
Thank you.
相关内容
- AWS 官方已更新 3 年前
Find the stacktrace in the log to try to figure out what is trying to connect to what