Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PingInSeconds 60 and MaxPings 10 is a bit low. #5

Open
fivethreeo opened this issue Jan 31, 2016 · 5 comments
Open

PingInSeconds 60 and MaxPings 10 is a bit low. #5

fivethreeo opened this issue Jan 31, 2016 · 5 comments

Comments

@fivethreeo
Copy link
Contributor

Deployment of elasicsearch many times exceeds 30 min.

@andrew-templeton
Copy link
Owner

Suggestion for solve? Parametrize it?

@fivethreeo
Copy link
Contributor Author

Wont that require redoing cfn-lamda a lot? Maybe make it configurable from the deploy script with args or a prompt.

@fivethreeo
Copy link
Contributor Author

On second thought parametrize seems like a better choice, but has to be done in cfn-lambda.

@fivethreeo
Copy link
Contributor Author

Something like:

      if (Params.PingInSeconds) longRunningConf.PingInSeconds = Params.PingInSeconds;
      if (Params.MaxPings) longRunningConf.MaxPings = Params.MaxPings;

@andrew-templeton
Copy link
Owner

hmmmmm.... Probably best approach - might make it all lowercase, and add argparser to cfn-lambda?

--ping-interval XX --ping-max YY ?

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

No branches or pull requests

2 participants