Hi Raj,
Yes your observation is correct. But in the CEP extension it expect stats
within one minute. So it send member faulty event after one minute.
Thanks !
On Fri, Oct 10, 2014 at 11:14 PM, Akila Ravihansa Perera wrote:
> On Fri, Oct 10, 2014 at 11:09 PM, Rajkumar Rajaratnam
> wrote:
> > H
On Fri, Oct 10, 2014 at 11:09 PM, Rajkumar Rajaratnam
wrote:
> Hi
>
> On Fri, Oct 10, 2014 at 10:42 PM, Akila Ravihansa Perera
> wrote:
>>
>> Hi Raj,
>>
>> What you provide in GradientOfHealthRequest.xml execution plan is the
>> time period that CEP waits to execute the Siddhi Window Processor.
>
Hi
On Fri, Oct 10, 2014 at 10:42 PM, Akila Ravihansa Perera wrote:
> Hi Raj,
>
> What you provide in GradientOfHealthRequest.xml execution plan is the
> time period that CEP waits to execute the Siddhi Window Processor.
> This is not exactly the time period Stratos will wait to detect faulty
> i
Also I don't think you can change the time out period on the fly. You
have to restart the server to make changes take effect. Have you
succeeded in changing this value on the fly? This value is read once
and kept in memory according to the logic in Window processor init
method.
I think there is mo
Hi Raj,
What you provide in GradientOfHealthRequest.xml execution plan is the
time period that CEP waits to execute the Siddhi Window Processor.
This is not exactly the time period Stratos will wait to detect faulty
instances. It is defined by TIME_OUT variable in
FaultHandlingWindowProcessor.java
On Fri, Oct 10, 2014 at 10:34 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> Hi Raj,
>
> I don't think this is configurable. Timeout period is hard coded in the
> fault handling window processor at the movement [1].
>
Even though it is hard coded there, if we run the fault handli
Hi Raj,
I don't think this is configurable. Timeout period is hard coded in the
fault handling window processor at the movement [1].
[1]
https://github.com/apache/stratos/blob/master/extensions/cep/stratos-cep-extension/src/main/java/org/apache/stratos/cep/extension/FaultHandlingWindowProcessor.j
Hi Manas,
Seems it is configurable. We do not need to build the stratos again. We
don't need to even restart the stratos.
You can edit the following file in your running stratos setup.
Please edit the following file;
/apache-stratos-default/repository/deployment/server/executionplans/GradientOf
idge & it comes Active within
>> the expiry-timeout mentioned above. Now, after sometime the cartridge vm
>> becomes unreachable or disconnected than based on which timer, stratos will
>> decide to delete the cartridge-vm & re-spawn the new instance of it.
>>
>>
>&g
declare that
> cartridge as faulty-vm??
>
>
>
> Regards
>
> Manas.
>
>
>
> *From:* Rajkumar Rajaratnam [mailto:rajkum...@wso2.com]
> *Sent:* Friday, October 10, 2014 7:14 PM
> *To:* dev@stratos.apache.org
>
> *Subject:* Re: Which Timer in Strato
os will decide to
delete the cartridge-vm & re-spawn the new instance of it.
Regards
Manas
From: Lasindu Charith [mailto:lasi...@wso2.com<mailto:lasi...@wso2.com>]
Sent: Friday, October 10, 2014 6:29 PM
To: dev
Subject: Re: Which Timer in Stratos Triggers Cartridge Deletion When it
ich timer, stratos will
> decide to delete the cartridge-vm & re-spawn the new instance of it.
>
>
>
> Regards
>
> Manas
>
>
>
>
>
>
>
>
>
> *From:* Lasindu Charith [mailto:lasi...@wso2.com]
> *Sent:* Friday, October 10, 2014 6:29 PM
> *To:*
e or disconnected than based on which timer, stratos will decide to
delete the cartridge-vm & re-spawn the new instance of it.
Regards
Manas
From: Lasindu Charith [mailto:lasi...@wso2.com]
Sent: Friday, October 10, 2014 6:29 PM
To: dev
Subject: Re: Which Timer in Stratos Triggers C
Hi Manas,
You should change the member 'expiryTimeout' property in
/repository/conf/autoscaler.xml in order to adjust the
timeout value.
Thanks,
On Fri, Oct 10, 2014 at 6:18 PM, Manas Padegaonkar -T (mpadegao - ARICENT
TECHNOLOGIES HOLDINGS LIMITED at Cisco) wrote:
> Hi,
>
>
>
> Wanted to kno
14 matches
Mail list logo
