I have removed this unnecessary thread sleep in commit
26f0c4e0a80b773733aff2b37f5458. I have tested with mock and k8s and found
no issues.

Thanks,
Raj.

On Fri, Nov 13, 2015 at 11:12 AM, Reka Thirunavukkarasu <r...@wso2.com>
wrote:

> +1. fine then..:)
>
> Thanks,
> Reka
>
> On Fri, Nov 13, 2015 at 11:09 AM, Rajkumar Rajaratnam <rajkum...@wso2.com>
> wrote:
>
>> Hi Reka,
>>
>> Yes, that's what we are going to do. We are going to start event receiver
>> threads after syncing the registry with in-memory model.
>>
>> Thanks,
>> Raj.
>>
>> On Fri, Nov 13, 2015 at 11:06 AM, Reka Thirunavukkarasu <r...@wso2.com>
>> wrote:
>>
>>> In that case, can't we simply start these Receiver threads atlast after
>>> done with all the registry loading the component activation?
>>>
>>>
>>> Thanks,
>>> Reka
>>>
>>> On Fri, Nov 13, 2015 at 11:05 AM, Rajkumar Rajaratnam <
>>> rajkum...@wso2.com> wrote:
>>>
>>>> Akila, sure - will fix it.
>>>>
>>>> On Fri, Nov 13, 2015 at 11:02 AM, Akila Ravihansa Perera <
>>>> raviha...@wso2.com> wrote:
>>>>
>>>>> 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
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Rajkumar Rajaratnam
>>>> Committer & PMC Member, Apache Stratos
>>>> Software Engineer, WSO2
>>>>
>>>> Mobile : +94777568639
>>>> Blog : rajkumarr.com
>>>>
>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>


-- 
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2

Mobile : +94777568639
Blog : rajkumarr.com

Reply via email to