Thanks for the clarification Isuru! @Raj: will you be able to fix this as part of the fix that you are doing to AS related to topology receiver?
Thanks. On Fri, Nov 13, 2015 at 10:58 AM, Isuru Haththotuwa <isu...@apache.org> wrote: > This can be similar to the issue Raj has explained in thread [1]. The > HealthStat receiver is started before the information is loaded from the > registry. We should start the HealthStat and Topology threads after loading > the information from the registry. That might be the reason why we are > waiting 15s till all information is loaded to the memory. > > > [1]. [Stratos 4.1.5] [Blocker] Monitors are not created on Stratos restart > > On Fri, Nov 13, 2015 at 10:47 AM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Any thoughts please? >> >> On Wed, Nov 11, 2015 at 11:26 PM, Akila Ravihansa Perera < >> raviha...@wso2.com> wrote: >> >>> Hi devs, >>> >>> I noticed $subject in [1]. Is there any reason for this? As per a >>> comment it is waiting for Autoscaler deployer to be activated. Anyone has >>> an idea what this is about? >>> >>> 15s delay at the server startup is a significant amount of delay. If >>> this is actually needed we need to fix this properly. >>> >>> [1] >>> https://github.com/apache/stratos/blob/stratos-4.1.x/components/org.apache.stratos.autoscaler/src/main/java/org/apache/stratos/autoscaler/event/receiver/health/AutoscalerHealthStatEventReceiver.java#L55 >>> >>> >>> Thanks. >>> >>> -- >>> Akila Ravihansa Perera >>> WSO2 Inc.; http://wso2.com/ >>> >>> Blog: http://ravihansa3000.blogspot.com >>> >> >> >> >> -- >> Akila Ravihansa Perera >> WSO2 Inc.; http://wso2.com/ >> >> Blog: http://ravihansa3000.blogspot.com >> > > > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* <http://wso2.com/>* > > > -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com
