Thanks, is the idle time configurable?
On Fri, Apr 25, 2014 at 2:43 PM, Dannon Baker <dannon.ba...@gmail.com>wrote:
> You can review the exact code here( see 'slow_job_turnover') :
> But, basically, load on any particular node isn't very useful for
> autoscaling in this context because most jobs cannot be split among
> multiple nodes. What we use is a heristic to determine churn and jobs
> waiting to run. Generally speaking, if you have jobs waiting to run for a
> bit, your cluster should scale.
> On Fri, Apr 25, 2014 at 2:37 PM, Jim McCusker
>> What are the exact conditions that will trigger autoscaling in a
>> galaxy/cloudman instance? I'm seeing 100% utilization on the head node but
>> no attempts by cloudman at spinning up new instances. What sort of state is
>> supposed to trigger that?
>> Please keep all replies on the list by using "reply all"
>> in your mail client. To manage your subscriptions to this
>> and other Galaxy lists, please use the interface at:
>> To search Galaxy mailing lists use the unified search at:
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: