jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luciano Sabença (JIRA) <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-624) Bug at ListNodes In ChefContext
Date Mon, 04 Aug 2014 17:40:12 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084949#comment-14084949
] 

Luciano Sabença commented on JCLOUDS-624:
-----------------------------------------

A little late, but just to thank you!
I'm glad to do a little contribution to this amazing project!

> Bug at ListNodes In ChefContext
> -------------------------------
>
>                 Key: JCLOUDS-624
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-624
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-chef
>    Affects Versions: 1.7.3
>            Reporter: Luciano Sabença
>            Assignee: Ignasi Barrera
>             Fix For: 1.8.0
>
>
> Hi.
> I've found a bug when using ListNodes in jclouds-chef. The problem is related to the
thread pool that is used when ListNodes is called. 
> When using ListNodes, for each node that exists in Chef, a new task is submitted to the
pool "USER_THREADS". Each one of these submitted tasks generates another Runnable - to do
the HTTP request -  and submits it to the same thread pool. So, when we have a large number
of nodes(an usual scenario when dealing with Chef), all threads in the pool are blocked waiting
its own thread responsible to do the HTTP request and no thread is left to effectively do
the HTTP request. After the configured timeout, a lot of java.util.concurrent.TimeoutException
are thrown.
> I am already working to fix it and I will release a pull request soon (maybe, in a few
days).
> Thanks



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message