Skip to content
This repository has been archived by the owner on Feb 9, 2019. It is now read-only.

EC2 Instances starts a start and stop looping after the instance is stopped by scheduler #19

Open
mvinii94 opened this issue Nov 23, 2017 · 3 comments

Comments

@mvinii94
Copy link

Hi,

It seems that this solution is not working anymore, the EC2 instance starts a looping where its state changes to stop and start after the instance is stopped by the first time by the script.

It seems that the solution does not honor the start and stop time setup on the tag and keeps starting and stopping the EC2 instances everytime that the lambda is invoked.

Could you please take a look at it?

Thanks in advance.

@jasonhsiac10
Copy link

Hi,

Do you have your start and stop time very close? i.e. within 1 hour?

I get the same experience when the start and stop time is configured too close, and i think it is coded that way to allow the retries.
Cheers
Jason

@mvinii94
Copy link
Author

Hi Jason,

The start/stop depends on the Lambda's event schedule period. If you set to 1 hour it will happen in 1 hour, if you set to 1 minute the instance will be starting and stopping every minute.

As I mentioned in the issue, it seems that the script does not honor the starting/stopping time on the tag and starts/stops the instances everytime that the Lambda Function is invoked.

Cheers.

@Nano803
Copy link

Nano803 commented Feb 1, 2018

I'm facing the same situation. Any plans to solve it?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants