vinodkc opened a new pull request #32638:
URL: https://github.com/apache/spark/pull/32638


   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: 
https://spark.apache.org/contributing.html
     2. Ensure you have added or run the appropriate tests for your PR: 
https://spark.apache.org/developer-tools.html
     3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., 
'[WIP][SPARK-XXXX] Your PR title ...'.
     4. Be sure to keep the PR description updated to reflect all changes.
     5. Please write your PR title to summarize what this PR proposes.
     6. If possible, provide a concise example to reproduce the issue for a 
faster review.
     7. If you want to add a new configuration, please read the guideline first 
for naming configurations in
        
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
     8. If you want to add or modify an error message, please read the 
guideline first:
        https://spark.apache.org/error-message-guidelines.html
   -->
   
   ### What changes were proposed in this pull request?
   This PR aims to upgrade Apache HttpCore from 4.4.12 to 4.4.14.
   
   ### Why are the changes needed?
   Stability improvements
   
   - Bug fix: Non-blocking TLSv1.3 connections can end up in an infinite event 
spin when closed concurrently by the local and the remote endpoints.
   - HTTPCORE-647: Non-blocking connection terminated due to 
'java.io.IOException: Broken pipe' can enter an infinite loop flushing buffered 
output data.
   - PR #201, HTTPCORE-634: Fix race condition in AbstractConnPool that can 
cause internal state
   -   corruption
   - HTTPCORE-612: DefaultConnectionReuseStrategy incorrectly used int to 
represent Content-Length value
   -   instead of long
   
   ### Does this PR introduce _any_ user-facing change?
   No
   
   ### How was this patch tested?
    With Jenkins Tests
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to