stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nirmal Fernando <nirmal070...@gmail.com>
Subject Re: Failed to terminate member Error appearing repeatedly
Date Tue, 28 Oct 2014 09:55:09 GMT
MemberSpawned event will update it, isn't it?

On Tue, Oct 28, 2014 at 10:53 AM, Rajkumar Rajaratnam <rajkumarr@wso2.com>
wrote:

> Seems we are having a problem here. If we are adding to the topology as
> soon as CC gets a instance start up call, at that point we do not have
> information such as member ip, allocated port and so on. If we add it to
> the topology at this point, then we might need to update topology again
> once we get this information, right?
>
> Thanks.
>
> On Tue, Oct 28, 2014 at 3:16 PM, Rajkumar Rajaratnam <rajkumarr@wso2.com>
> wrote:
>
>>
>>
>> On Tue, Oct 28, 2014 at 3:00 PM, Nirmal Fernando <nirmal070125@gmail.com>
>> wrote:
>>
>>> I think the correct approach would be to introduce a new topology event
>>> to fill the blind area between real instance creation via CC and member
>>> spawned event. So, as soon as CC receives a instance start up call, CC
>>> would add the member to topology and will send a new event with a new state
>>> possibly.
>>>
>>
>> Yes, the idea I proposed is a hacky way. So with the new event, we are
>> guarantee to have the member in the topology once AS asks CC to spawn an
>> instance. Seems this is a good idea :) I will implement it.
>>
>> Thanks Nirmal.
>>
>>
>>>
>>> On Tue, Oct 28, 2014 at 10:06 AM, Chamila De Alwis <chamilad@wso2.com>
>>> wrote:
>>>
>>>>
>>>> Hi Raj,
>>>>
>>>>
>>>> On Tue, Oct 28, 2014 at 2:23 PM, Rajkumar Rajaratnam <
>>>> rajkumarr@wso2.com> wrote:
>>>>
>>>>> CC will add it to the topology, send member created event and send
>>>>> member terminated soon after that. Now AS will get this event and remove
>>>>> the member from its lists. We can't send member terminated events for
>>>>> members which are not in the topology. If we do so, these events will
be
>>>>> rejected by message processors.
>>>>
>>>>
>>>> Is it logically correct to send a member created event for a member
>>>> that is obsolete? Can't we allow a new path to complete termination
>>>> sequence for an obsolete member?
>>>>
>>>>
>>>> Regards,
>>>> Chamila de Alwis
>>>> Software Engineer | WSO2 | +94772207163
>>>> Blog: code.chamiladealwis.com
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Software Engineer | WSO2, Inc.
>> Mobile +94777568639 | +94783498120
>>
>
>
>
> --
> Rajkumar Rajaratnam
> Software Engineer | WSO2, Inc.
> Mobile +94777568639 | +94783498120
>



-- 
Best Regards,
Nirmal

Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.

Blog: http://nirmalfdo.blogspot.com/

Mime
View raw message