.0,"scaleDownMarginOfGradient":1.0,"scaleDownMarginOfSecondDerivative":0.2}}}
And this deployment policy :
{"id":"autoscale-1-2","partitionGroup":[{"id":"N1","partitionAlgo":"one-after-another","partition
similar issue?
Thanks,
Reka
On Mon, Aug 11, 2014 at 7:51 PM, David Waddell
mailto:david.wadd...@owmobility.com>> wrote:
Hi guys
Just wondering if was anybody able to look at this ? As we're just not
sure if we are setup incorrectly or if there are issues in the autoscaler.
Thanks
Hi guys
Just wondering if was anybody able to look at this ? As we're just not
sure if we are setup incorrectly or if there are issues in the autoscaler.
Thanks again
David
-Original Message-
From: David Waddell [mailto:david.wadd...@owmobility.com]
Sent: 08 August 2014 16:
Is it possible we are misconfigured and should not have multiple
subscriptions in a network partition ? Or are these genuine issues ?
Thanks
David.
-----Original Message-
From: David Waddell
Sent: 06 August 2014 16:40
To: 'Akila Ravihansa Perera'
Cc: dev@stratos.apache.or
origin ?
Thanks
David.
-Original Message-
From: Akila Ravihansa Perera [mailto:raviha...@wso2.com]
Sent: 06 August 2014 16:28
To: David Waddell
Cc: dev@stratos.apache.org; Shaheed Haque
Subject: Re: autoscaler issue with multiple cartridges + subscriptions
Hi David,
Seems like the Drool
.. clarified cartridges/policies inline below..
-Original Message-
From: David Waddell [mailto:david.wadd...@owmobility.com]
Sent: 06 August 2014 13:46
To: Akila Ravihansa Perera; dev
Cc: Shaheed Haque
Subject: RE: autoscaler issue with multiple cartridges + subscriptions
Hi Guys
ility of enabling following logger in the
>> log4j.properties file ?
>>
>> log4j.logger.org.apache.stratos.autoscaler.rule.RuleLog=DEBUG
>>
>>
>> For each service cluster, we run a Cluster Monitor and that is
>> responsible for monitoring and scaling the cluster.
>>
>>
>>
>> On T
