Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

By Jason Gegere
Hello.
I have completed these guides provided by DigitalOcean and feel very confident. https://www.digitalocean.com/community/tutorial_series/getting-started-with-coreos-2
I had 3 x 512mb Droplets running great. I decided to spin up 3 x 1gb Droplets using the same “discovery” token.
I was able to run:
core@coreos-1 ~ $ fleetctl list-machines
MACHINE IP METADATA
3c5fc75c... 10.132.191.194 public_ip=104.236.56.224,region=nyc
3f45fcd6... 10.132.192.113 public_ip=104.236.63.141,region=nyc
6aab38ca... 10.132.189.117 public_ip=104.236.47.209,region=nyc
b851ef0f... 10.132.189.118 public_ip=104.236.47.210,region=nyc
cd30023e... 10.132.189.116 public_ip=104.236.47.208,region=nyc
d378e962... 10.132.191.193 public_ip=104.236.56.222,region=nyc
Returning all the correct information. I then decided to take down the 3 x 512mb systems thinking that everything should cycle correctly.
When I SSH into the remaining 3 x 1gb Droplets and run “fleetctl list-machines”
There is a problem:
$ fleetctl list-machines
2014/11/03 23:13:48 INFO client.go:278: Failed getting response from http://127.0.0.1:4001/: too many redirects
2014/11/03 23:13:48 ERROR client.go:200: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 100ms
Did I not give enough time before shutting down the initial 3 systems? How does the fleetctl process transfer roles if other nodes go offline?