I see. I didn¹t catch that. Thanks for the clarification! Mingyu
From: Matei Zaharia <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Friday, January 24, 2014 at 2:37 PM To: "[email protected]" <[email protected]> Subject: Re: Suggestion for ec2 script The issue is that ³start² is designed to restart the cluster after pausing the instances with ³stop², and because some instances¹ DNS names changed, we need to modify the master URL and the list of slaves in the various config files. If you make other changes in these config files, they will indeed be lost. One solution might be to create your own setup script to run on the instances after ³start². Matei On Jan 24, 2014, at 2:19 PM, Mingyu Kim <[email protected]> wrote: > Hi all, > > I found it confusing that "./spark-ec2 start² actually reinstalls the cluster, > which ends up wiping out all the configurations. How about renaming ³start² to > ³install² and add a real light-weight ³start² for frequently starting and > stopping ec2 instances for mostly cost reasons? The light-weight ³start² can > simply bring up the instances and invoke ³bin/start-all.sh². Thoughts? > > Mingyu
smime.p7s
Description: S/MIME cryptographic signature
