- Newest
- Most votes
- Most comments
It looks like the application is spending 100% of its time trying to connect to a socket, as indicated by the stack trace involving java.net.Socket.connect
, and specifically SSLConnectionFactory.connectSocket
. This suggests that the Flink job is not proceeding to the S3 write operation because it is stuck trying to establish an SSL connection, likely to Kafka, as there is no indication of S3 specific API calls in the stack trace.
Try these steps:
- Verify that the Flink application has the correct network access to the Kafka brokers and that no firewall or security group is blocking the required ports.
- If you're using SSL/TLS for the Kafka connection, verify that your truststore and keystore configurations are correct and that the Flink application can access the necessary files with the correct passwords.
- The problem seems to be before the S3 write operation, so make sure that the Flink application has the right permissions and configurations to write to the specified S3 bucket.
If you're unfamiliar with how to verify a security group, you can find detailed instructions in this article Networking 101 - Part 2, specifically in the section about security groups.
Seems like a connection issue. Have you checked eventual firewall rules that could block the communication?
Hi Cristian , Thanks for reply , Kindly suggest what are checks that I have to look in for firewall , We are at POC stage , If you could give step by step doc that could be great , We are building data pipelines source is aws managed kafka , AWS managed Flink process the JSON doc and write to S3 .. please sugest what are the checks that I look in here ,
Thanks
Relevant content
- asked a month ago
- asked 2 years ago
- asked 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago