[jira] [Updated] (JCLOUDS-628) PROPERTY_MAX_CONNECTIONS_PER_CONTEXT not honored for https connections

["Ignasi Barrera (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCLOUDS-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ignasi Barrera updated JCLOUDS-628:
-----------------------------------
    Fix Version/s:     (was: 2.0.0)
                   2.1.0

> PROPERTY_MAX_CONNECTIONS_PER_CONTEXT not honored for https connections
> ----------------------------------------------------------------------
>
>                 Key: JCLOUDS-628
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-628
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.7.3
>            Reporter: Shri Javadekar
>             Fix For: 2.1.0
>
>
> The property PROPERTY_MAX_CONNECTIONS_PER_CONTEXT in jclouds governs how many connections are open to an endpoint per blobstore context. This along with PROPERTY_MAX_CONNECTION_REUSE makes sure that we don't run out of ports or fds on the underlying OS.
> I ran a simple test for verifying the PROPERTY_MAX_CONNECTIONS_PER_CONTEXT option. I created a container with ~10K blobs. I then used jclouds-cli to clear the container.
> I explicitly set jclouds.max-connections-per-context to 20. When the endpoint was http, things worked just fine.
> $ netstat -a | grep blah | grep ESTABL | wc -l
>       20
> $ netstat -a | grep blah | grep ESTABL | wc -l
>       21
> $ netstat -a | grep blah | grep ESTABL | wc -l
>       20
> However, when the endpoint was https, this config option did not seem to be honored. The endpoint was https://api.atmosonline.com for the numbers below, but I also tried with a local swift endpoint which was https.
> $ netstat -a | grep atmos | grep ESTABL | wc -l
>      516
> $ netstat -a | grep atmos | grep ESTABL | wc -l
>      602
> I've already run into a situation where we exhausted all the available ports and operations such as container-clear or container-delete failed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)