[
https://issues.apache.org/jira/browse/STRATOS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajkumar Rajaratnam resolved STRATOS-919.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 4.1.0 Beta
This is resolved by adding the member context to CC data holder as soon as CC
gets an instance start up call from AS.
> Error while AS asks CC to terminate an instance that are not in the topology
> ----------------------------------------------------------------------------
>
> Key: STRATOS-919
> URL: https://issues.apache.org/jira/browse/STRATOS-919
> Project: Stratos
> Issue Type: Bug
> Components: Autoscaler, Cloud Controller, Messaging
> Affects Versions: 4.1.0 M2
> Reporter: Rajkumar Rajaratnam
> Priority: Critical
> Fix For: 4.1.0 M4, 4.1.0 Beta
>
>
> The following scenario will ended up with termination failed error
> continuously.
> AS asks CC to create a container
> CC schedule a new task and returning member contexts to AS
> AS adding the members to pending list
> CC is also adding member contexts to its data holder
> But CC will not add it to the topology until pods status become to "Running"
> state
> Meanwhile members are exceeding their timeouts and moved to obsolete list
> AS asks CC to terminate obsolete pods
> CC kills it, but didn't send the member terminated event, because member is
> not in the topology
> AS didn't get any member terminated event, so it will not remove any members
> from its member lists
> AS will ask CC again to terminate the pod, in next monitor interval
> CC now will complain "Failed to terminate member. Member id not found",
> because it terminated those pods already and removed the member contexts from
> its data holder
> So this "Failed to terminate member. Member id not found" will occur
> continuously
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
