Yes, I think open an issue in JIRA is good and I volunteer to help fixing this
Best, -- Nan Zhu On Saturday, March 1, 2014 at 11:49 PM, Nicholas Chammas wrote: > Should I open an issue in JIRA to track this as a minor bug? > > > On Sat, Mar 1, 2014 at 8:07 PM, Josh Rosen <[email protected] > (mailto:[email protected])> wrote: > > This seems like a bug; I think we should change the script to allow you to > > sign into a cluster without workers. > > > > Imagine that I launch a cluster using spot workers for the instances; if > > all of my workers die, I still want to be able to sign into the master (a > > non-spot instance) to retrieve job results or logs. > > > > > > On Sat, Mar 1, 2014 at 4:55 PM, Patrick Wendell <[email protected] > > (mailto:[email protected])> wrote: > > > Yep, currently it only supports running at least 1 slave. > > > > > > On Sat, Mar 1, 2014 at 4:47 PM, nicholas.chammas > > > <[email protected] (mailto:[email protected])> wrote: > > > > I successfully launched a Spark EC2 "cluster" with 0 slaves using > > > > spark-ec2. > > > > When trying to login to the master node with spark-ec2 login, I get the > > > > following: > > > > > > > > Searching for existing cluster test-blah... > > > > > > > > Found 1 master(s), 0 slaves > > > > > > > > ERROR: Could not find slaves in group test-blah-slaves > > > > > > > > > > > > Is this an oversight, or it is intended that I not be able to use a > > > > master-only cluster? > > > > > > > > Nick > > > > > > > > > > > > ________________________________ > > > > View this message in context: spark-ec2 login expects at least 1 slave > > > > Sent from the Apache Spark User List mailing list archive at Nabble.com > > > > (http://Nabble.com). > > >
