You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.
My question is around how to configure / identify all the mesos masters when they are in an auto scaling group running on AWS? Specifically, the "masters" parameter indicates that you need to enter the ip addresses of the master nodes. We could enter the current ip addresses of the master nodes but our concern is when / if there is a scaling event and a new master is added or a master node is taken away, we would need to update the config / restart the service. Is there a recommended approach for dealing with auto scaling in this case? Does the configuration have to identify all master nodes? Can it reference an elastic load balancer?
The text was updated successfully, but these errors were encountered:
Hello,
My question is around how to configure / identify all the mesos masters when they are in an auto scaling group running on AWS? Specifically, the "masters" parameter indicates that you need to enter the ip addresses of the master nodes. We could enter the current ip addresses of the master nodes but our concern is when / if there is a scaling event and a new master is added or a master node is taken away, we would need to update the config / restart the service. Is there a recommended approach for dealing with auto scaling in this case? Does the configuration have to identify all master nodes? Can it reference an elastic load balancer?
The text was updated successfully, but these errors were encountered: