stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nirmal Fernando (JIRA)" <>
Subject [jira] [Commented] (STRATOS-706) member terminate event should log reason
Date Wed, 16 Jul 2014 23:39:05 GMT


Nirmal Fernando commented on STRATOS-706:

On Thu, Jul 17, 2014 at 1:11 AM, Martin Eppel (JIRA) <>

All the log file you quoted is from Cloud Controller. And what CC does is
providing an API to terminate instances. The caller of this API, i.e.
auto-scaler is the one who logs the reason for calling CC to terminate
instances. Did you check auto-scaler logs?

Best Regards,

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


> member terminate event should log reason
> ----------------------------------------
>                 Key: STRATOS-706
>                 URL:
>             Project: Stratos
>          Issue Type: Bug
>          Components: Autoscaler
>    Affects Versions: 4.0.0
>            Reporter: Martin Eppel
>             Fix For: 4.0.1
> When Stratos terminates a member it must log the reason for it. Ideally the logging should
be systematic enough so that one can grep for different severity, or by member, or by event
type or some other useful categorization.
> The justification for this defect is that it will improve greatly debugging and troubleshooting
capabilities. Without logging it is very difficult to debug terminations of members.
> For example, consider this sequence in the stratos log file:
> ===================
> TID: [0] [STRATOS] [2014-07-15 09:58:48,654] DEBUG {}
-  Received an instance spawn request : MemberContext [memberId=null, nodeId=null,,
cartridgeType=null, privateIpAddress=null, publicIpAddress=null, allocatedIpAddress=null,
initTime=1405418328649, lbClusterId=null, networkPartitionId=OAM1] {}
> TID: [0] [STRATOS] [2014-07-15 09:58:48,654] DEBUG {}
> TID: [0] [STRATOS] [2014-07-15 09:58:55,888]  INFO {}
-  Member is terminated: MemberContext [,
cartridgeType=cisco-gilan-appmgr, privateIpAddress=, publicIpAddress=null, allocatedIpAddress=null,
initTime=1405417410736, lbClusterId=null, networkPartitionId=OAM1] {}
> ===================
> The problem is that Stratos gives no indication of why it is doing this [1]. Stratos
should be enhanced so that the above message gives some indication of *why* the member is
being terminated (loss of heartbeats, timeout on port knocking etc. etc.). This is needed
as apache stratos expands it's user base.
> This issue has high priority as it affects the efficiency of troubleshooting and system

This message was sent by Atlassian JIRA

View raw message