You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/02/19 19:06:20 UTC
[jira] [Commented] (JCLOUDS-459) Limit number of user threads
[ https://issues.apache.org/jira/browse/JCLOUDS-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905773#comment-13905773 ]
ASF subversion and git services commented on JCLOUDS-459:
---------------------------------------------------------
Commit c035bcd6b20063d79aaf270c19beed476dcb5c05 in jclouds's branch refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=c035bcd ]
JCLOUDS-459: Limit maximum user threads
Previously jclouds could use an unlimited number of threads on its
user ExecutorService. While this ExecutorService will go away when we
complete deasyncafication, we should prevent jclouds from misbehaving
until that time.
> Limit number of user threads
> ----------------------------
>
> Key: JCLOUDS-459
> URL: https://issues.apache.org/jira/browse/JCLOUDS-459
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
> Affects Versions: 1.7.1
> Reporter: Andrew Gaul
> Fix For: 1.8.0, 1.7.2
>
>
> Presently jclouds does not limit the number of user threads. While de-asyncification could address this in the long-term, in the short-term we should protect our users with some sane default. I suggest 20 or 50, the former mirroring the number of IO threads, and the latter sourced from my extensive testing of most blobstore providers. Note that Atmos providers have issues with large numbers of concurrent requests and errors from JCLOUDS-137 will occur. I work around these in my application by setting 10 IO and 10 user threads for Atmos Online and 8 and 8 for Synaptic Atmos.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)