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

No longer wait for nodetool for advanced users #5

Closed
joaquincasares opened this issue Jul 6, 2012 · 7 comments
Closed

No longer wait for nodetool for advanced users #5

joaquincasares opened this issue Jul 6, 2012 · 7 comments

Comments

@joaquincasares
Copy link
Contributor

Waiting for nodetool...
The cluster is now in it's finalization phase. This should only take a moment...

Will stay on the motd for a while if the service is not running. Simplify that screen to allow for those running the cluster not to see that.

@arodrime
Copy link

arodrime commented Oct 7, 2014

Regarding this, I see this message for 3 years now, obliging me to wait or ctrl-C on ssh connection. I never had any use of those messages. What is this useful for ? Can't we just get rid of this, giving immediate access to the machine, at least make this configurable so I can disable it. Ctrl-C works just fine, but day after day, and after 3 years, this become annoying.

@joaquincasares
Copy link
Contributor Author

That is a use case I had not really taken the time to consider. Originally the AMI was meant to show off the cluster to new Cassandra users.

I don't have the time to get to this today, but ideally we would add another option here:
https://github.com/riptano/ComboAMI/blob/2.5/ds2_configure.py#L223

Run a conf.set_config() here:
https://github.com/riptano/ComboAMI/blob/2.5/ds2_configure.py#L302

And add a check here:
https://github.com/riptano/ComboAMI/blob/2.5/ds4_motd.py#L242

I'll see if I can whip this up, test, and push this in the near future.

Thanks for bumping this issue!

@arodrime
Copy link

arodrime commented Oct 9, 2014

Ok great.

So this will be a setup option right ? Is there no way / wouldn't it be better to modify configuration on running instances to add or remove this option on running instances (or at least on instances launched after this patch, but still at run time) ?

Just a question, I do not really care since I will probably disable it once and for all but, maybe new users would like to have this at start and will later be annoyed by it. They won't be able to disable this then. Any thoughts regarding this ?

@joaquincasares
Copy link
Contributor Author

Indeed, all configurations passed to ds4_motd.py go through ~/datastax_ami/ami.conf so you'll be able to manually edit them.

Sorry for not thinking about this earlier, but try just commenting out this line in all your current instances: https://github.com/riptano/ComboAMI/blob/2.5/ds4_motd.py#L242

That should disable any more motd messages. :)

@arodrime
Copy link

This worked indeed.

I don't know why I did not take care of this a while ago :).

Thanks for the tip and your responsiveness, as always.

@joaquincasares
Copy link
Contributor Author

No worries, glad to have helped.

@mlococo
Copy link
Contributor

mlococo commented Jun 5, 2015

I'm going to close this wontfix. With the new --repository feature it's easier than ever to add site-specific customizations like this for folks that do want it, and the AMI is really intended as a demo setup rather than for long-lived production clusters.

@mlococo mlococo closed this as completed Jun 5, 2015
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

3 participants