Details
-
Type:
Story
-
Status: Raw
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.0.0
-
Fix Version/s: None
-
Component/s: S3
-
Labels:
-
Story Points:2
-
Epic Link:
-
Notability:4
Description
The AWS SDK for S3 defaults to a max of 50 connections. If more than 50 connections are leased in the pool it will lead to exceptions. One observed case of this leads to a permanent state where the connections are stuck. We should expose options to increase the connection pool limit, change failure behavior, retry policies and/or timeout configuration.
Acceptance criteria
- Advanced client configuration options are exposed and used
Other notes: Each S3 blob store creates its own client with corresponding connection pool. httpcomponents documentation (admittedly version 3 and not 4) specifies to try and share the HttpClient in a single application. http://hc.apache.org/httpclient-3.x/performance.html
Attachments
Issue Links
- relates
-
NEXUS-20152 S3 Blob Store: Timeout waiting for connection from pool
-
- Closed
-