This question has been archived.

CoreOS Fleet Clustering High Availability Problem

March 9, 2016 1.9k views
High Availability Clustering Docker CoreOS

i lunched two instanced with CoreOS and etcd setup. launched a sample service with Fleet.

Now for the test purposes, I shut down one of the machines.

Now fleetctl is giving me this error

Error retrieving list of units from repository: googleapi: Error 503: fleet server unable to communicate with etcd

I thought CoreOS and Fleet is High Availability solution, i dont understand why shutting down one machine caused this problem

Can anyone please help??

Be the first one to answer this question.