Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
4.0.0 Alpha
-
None
Description
It looks like un-subscription functionality is not working as expected.
Scenario:
1. Deploy a cartridge.
2. Subscribe to it.
3. Wait until an instance is activated.
4. Execute Un-subscribe option.
5. Now the running instances are terminated, but after some time new instances are spawned to replace the missing ones.
[2014-03-05 08:35:07,541] INFO
{org.apache.stratos.messaging.message.processor.topology.MemberMaintenanceModeProcessor} - Member updated as In_Maintenance: [service] php [cluster] im-php1.php.domain [member] im-php1.php.domainf73083ea-588a-4041-b817-8b86b13852d7
[2014-03-05 08:35:07,542] DEBUG
- Member has been moved as pending termination: [member] im-php1.php.domainf73083ea-588a-4041-b817-8b86b13852d7
[2014-03-05 08:35:07,542] DEBUG
- Active member is removed and added to the termination pending member list. [Member Id] im-php1.php.domainf73083ea-588a-4041-b817-8b86b13852d7
[2014-03-05 08:35:07,545] INFO
- Member updated as Ready to shutdown: [service] php [cluster] im-php1.php.domain [member] im-php1.php.domainf73083ea-588a-4041-b817-8b86b13852d7
[2014-03-05 08:35:14,488] INFO
{org.apache.stratos.autoscaler.client.cloud.controller.CloudControllerClient}- Trying to spawn an instance via cloud controller: [cluster] im-php1.php.domain [partition] zone-1 [lb-cluster] lb332185292.lb.domain [network-partition-id] ec2-region1