-
Notifications
You must be signed in to change notification settings - Fork 2
DC\OS FAQ
This is a collection of Frequently Asked Questions from our Slack channels. We've just started building up this content and will be adding to it on a regular basis. If you have anything which you think would be useful to our community, please add it here. You may also find your question answered in the official Mesosphere Support Knowlege Base, or the unofficial DC/OS field notes.
Can I add master nodes to an already deployed cluster ?
No, you can't scale master nodes in DC/OS or Mesos. You would need to create a new cluster with more masters.
Can I shut down my cluster and restart it later?
No, a complete shutdown isn't supported. If you're interested in backing up and restoring your cluster, you can get some ideas from the unsupported method described in this video
Can I use resources more efficiently by putting my master node on the same host as an agent?
Nope, each DC/OS node needs its own machine (which can be physical or virtual)
If I need to use an HTTP proxy in all my containers for north-south traffic, what do I need to configure as "no-proxy" for internal cluster services ?
A reasonable list seems to be :
.mesos
.thisdcos.directory
.dcos.directory
.zk
127.0.0.1
localhost
DNS resolution from inside my cluster to external hosts is intermittent
This may happen if you set a number of upstream resolvers before your local resolver in config.yml, due to the way DNS resolution will round robin to attempt to resolve an entry.
resolvers:
- 8.8.8.8
- 8.8.4.4
- private local DNS
The solution to this is to only set your local DNS in config.yml and handle forwarding in your local DNS server.
resolvers:
- private local DNS
How do I authenticate automated processes to run commands against the DCOS API ?
Authentication tokens provide a mechanism for authenticating automatically, although they have an expiry period (default 5 days) and may need to be renewed.
How can I get my OAuth API token to last more than 5 days?
See this blog post and thread on the mailing list for an unsupported fix.
How can I run a process on every agent node ?
Set the instance count for the task higher than the number of cluster nodes, and specifying unique hostname constraint. This method doesn't allow you to run the task on master nodes, only agents.
Why do tasks only launch on private agents? The only thing that will run on my public agents is Marathon-LB.
DC/OS launches your workloads on private agents to protect them from outside tampering, and to uses public nodes only for load balancing traffic from outside the cluster. Unless you have some good reason to launch your tasks on public nodes, they should be on private ones, with outside access controlled by a load balancer. You can learn more about DC/OS node types in the Node Type documentation.
How can I access Kafka brokers from outside my DC/OS cluster?
See this GitHub issue.
dcos.io