dcos

问题 I'm running DC/OS 1.7 with marathon-lb. spray.io 1.3.3 is returning 400 to all marathon-lb/HAProxy heath check calls: request has a relative URI and is missing a Host header so marathon-lb never routes any requests to the service. The health check in the marathon json is: "healthChecks": [ { "path": "/health", "protocol": "HTTP", "portIndex": 0, "gracePeriodSeconds": 10, "intervalSeconds": 2, "timeoutSeconds": 10, "maxConsecutiveFailures": 10, "ignoreHttp1xx": false } ], and the logging by

问题 I'm running DC/OS 1.7 with marathon-lb. spray.io 1.3.3 is returning 400 to all marathon-lb/HAProxy heath check calls: request has a relative URI and is missing a Host header so marathon-lb never routes any requests to the service. The health check in the marathon json is: "healthChecks": [ { "path": "/health", "protocol": "HTTP", "portIndex": 0, "gracePeriodSeconds": 10, "intervalSeconds": 2, "timeoutSeconds": 10, "maxConsecutiveFailures": 10, "ignoreHttp1xx": false } ], and the logging by

问题 I'm running DC/OS 1.7 with marathon-lb. spray.io 1.3.3 is returning 400 to all marathon-lb/HAProxy heath check calls: request has a relative URI and is missing a Host header so marathon-lb never routes any requests to the service. The health check in the marathon json is: "healthChecks": [ { "path": "/health", "protocol": "HTTP", "portIndex": 0, "gracePeriodSeconds": 10, "intervalSeconds": 2, "timeoutSeconds": 10, "maxConsecutiveFailures": 10, "ignoreHttp1xx": false } ], and the logging by

问题 I'm new to DC/OS and tried to install dcos-vagrant by following the guide on https://github.com/dcos/dcos-vagrant/blob/master/docs/deploy.md. While running vagrant up m1 a1 a2 a3 boot I get the following warnings: ==> m1: WARNING: bridge-nf-call-iptables is disabled ==> m1: WARNING: bridge-nf-call-ip6tables is disabled After the installation I can connect to the webapp on http://m1.dcos and it seems that DC/OS is running. But if I try deploying some applications the nodes cant connect to each

问题 I have got a cluster with gpu nodes (nvidia) and deployed DC/OS 1.8. I'd like to enable to schedule jobs (batch and spark) on gpu nodes using gpu isolation. DC/OS is based on mesos 1.0.1 that supports gpu isolation. 回答1: Unfortunately, DC/OS doesn't officially support GPUs in 1.8 ( experimental support for GPUs will be coming in the next release as mentioned here: https://github.com/dcos/dcos/pull/766 ). In this next release, only Marathon will officially be able to launch GPU services

问题 I have got a cluster with gpu nodes (nvidia) and deployed DC/OS 1.8. I'd like to enable to schedule jobs (batch and spark) on gpu nodes using gpu isolation. DC/OS is based on mesos 1.0.1 that supports gpu isolation. 回答1: Unfortunately, DC/OS doesn't officially support GPUs in 1.8 ( experimental support for GPUs will be coming in the next release as mentioned here: https://github.com/dcos/dcos/pull/766 ). In this next release, only Marathon will officially be able to launch GPU services

问题 I have installed HDFS from universe on my DCOS cluster of 10 Core OS machines (3 master nodes, 7 agent nodes). My HA HDFS config has 2 name nodes, 3 journal nodes and 5 data nodes. Now, my question is. Shouldn’t the HDFS be resilient to machine restarts? If I restart a machine where a data node is installed the data node gets rebuilt as a mirror of the others (only after restarting the HDFS service from the DC/OS UI). In the case of a restart where a journal node or a name node is, the nodes

问题 I have a production DC/OS(v1.8.4) cluster and I am trying to setup a Cassandra cluster inside it. I use Marathon(v1.3.0) to deploy Cassandra nodes. I use the official Docker image of Cassandra and more specifically the 2.2.3 version. First Case: Deploy Cassandra using HOST mode network - Everything OK In this case, I first deploy a node that I call cassasndra-seed and it attaches to a physical host with IP 10.32.0.6. From the stdout log of Marathon for this service I can see that "Node /10.32

问题 I have a production DC/OS(v1.8.4) cluster and I am trying to setup a Cassandra cluster inside it. I use Marathon(v1.3.0) to deploy Cassandra nodes. I use the official Docker image of Cassandra and more specifically the 2.2.3 version. First Case: Deploy Cassandra using HOST mode network - Everything OK In this case, I first deploy a node that I call cassasndra-seed and it attaches to a physical host with IP 10.32.0.6. From the stdout log of Marathon for this service I can see that "Node /10.32

问题 Is there any link/documentation available around installing DC/OS on Google Compute Engine where instances are ubuntu 16.04 instances including the bootstrap node instead of CentOS 7? Currently , the documents I find use Ansible and CentOS 7 on GCE as below. https://dcos.io/docs/1.7/administration/installing/cloud/gce/ 回答1: Short answer : Debian based distributions are currently (at least up to DC/OS 1.10) not supported. Long answer : It's possible, but requires some extra steps. DC/OS doesn