-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Intermittent stall of S3 PUT request for about 17 minutes #3110
Labels
bug
This issue is a bug.
third-party
This issue is related to third-party libraries or applications.
Comments
gudladona
added
bug
This issue is a bug.
needs-triage
This issue or PR still needs to be triaged.
labels
May 13, 2024
bhoradc
added
third-party
This issue is related to third-party libraries or applications.
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
May 14, 2024
Hi @gudladona, Thank you for reporting the issue. I see that you have also opened a Support ticket for the same. We will continue to provide support through the ticket you have opened. I will mark this as Closing-soon, to avoid duplicate efforts. Kindly send your questions through the Support case. Thanks. Regards, |
bhoradc
added
the
closing-soon
This issue will close in 2 days unless further comments are made.
label
May 14, 2024
ok, Thanks for the response. Can you kindly post the initial assessment if you have one already? |
github-actions
bot
removed
the
closing-soon
This issue will close in 2 days unless further comments are made.
label
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
This issue is a bug.
third-party
This issue is related to third-party libraries or applications.
Upcoming End-of-Support
Describe the bug
Hello,
We have an interesting problem that happens intermittently in our environment that causes the S3 PUT via HTTP PUT operation stall between 17-19 minutes. Let me try to describe this in detail.
First of, Environment details. We are running OSS spark and Hadoop on EKS with Karpenter.
JDK version : 11.0.19
Spark Version: 3.4.1
Hadoop Version: 3.3.4
EKS Version: 1.26
Hudi Version: 0.14.x
OS: Verified on both Bottlerocket & AL2
Issue Details:
Occasionally, we notice that Spark stage & few tasks get stalled for about 17 minutes, this delay is consistent whenever it happens. We have noticed that this is due to a stalled socket write on a close() within AWS SDK which uses Apache HTTP Client. When we expect a bad TLS connection, and the underlying socket should be terminated eagerly for a retry we don’t see that happening. Instead, the Socket is left until OS triggers a terminate. This seems to be due to the implementation of socket Linger option which is set to -1 by default in the JDK. An option exists to set Linger to 0 which means bad connections are immediately removed. But neither the AWS SDK nor the Apache HTTP Client sets this option to alter the default Linger behavior in the JDK.
Attached are the logs with slightly different errors with DEBUG level for AWS SDK and Hadoop S3a and Apache HTTP Client with when the issue is encountered.
After further investigation we have found this JDK bug : https://bugs.openjdk.org/browse/JDK-8241239. This perfectly describes and reproduces the issue we are having.
We have tried to fork the aws sdk by adding the LINGER option with default to 0 in here and set it to the SSL socket options here. But that did not fix the issue, which could be due to how the JDK version is treating the socket options.
Expected Behavior
The socket file descriptor should close non-gracefully/"prematurely", forcing the write to terminate immediately.
Current Behavior
close() blocks until the OS forces the socket closed at the transport layer, causing the socket write to fail
Reproduction Steps
As mentioned in https://bugs.openjdk.org/browse/JDK-8241239
Possible Solution
Assuming the right implementation of the LINGER by jdk, it would be good to allow users to set this ClientConfiguration.java which gets set into Apache HTTP Client settings.
Additional Information/Context
No response
AWS Java SDK version used
1.12.26
JDK version used
OpenJDK Runtime Environment Temurin-11.0.19+7
Operating System and version
BottleRocket & AL2
Logs & Other Attachments
aws+sdk+httpclient+debug.log
The text was updated successfully, but these errors were encountered: