Details

    • Type: Bug
    • Status: Resolved
    • Priority: High
    • Resolution: Won't Do
    • Affects Version/s: Marathon 1.5.2
    • Fix Version/s: None
    • Component/s: Networking
    • Labels:

      Description

      Hi!

      I'm trying to launch a pod with the following JSON configuration:

       

      {
        "id": "/druid",
        "version": "2018-01-10T09:32:26.109Z",
        "environment": {
          "key": "value"
        },
        "containers": [
          {
            "name": "broker",
            "resources": {
              "cpus": 0.5,
              "mem": 5120,
              "disk": 0
            },
            "image": {
              "kind": "DOCKER",
              "id": "my_image"
            },
            "healthCheck": {
              "http": {
                "scheme": "HTTP",
                "endpoint": "broker",
                "path": "/status"
              },
              "gracePeriodSeconds": 300,
              "intervalSeconds": 60,
              "maxConsecutiveFailures": 3,
              "timeoutSeconds": 20,
              "delaySeconds": 15
            },
            "endpoints": [
              {
                "name": "broker",
                "containerPort": 8082,
                "hostPort": 0,
                "protocol": [
                  "tcp"
                ],
                "labels": {
                  "VIP_0": "/druid:8082"
                }
              }
            ],
            "volumeMounts": [
              {
                "name": "hdfs",
                "mountPath": "/etc/hadoop/conf"
              }
            ]
          }
        ],
        "volumes": [
          {
            "name": "hdfs",
            "host": "/etc/hadoop/conf"
          }
        ],
        "networks": [
          {
            "name": "dcos",
            "mode": "container"
          }
        ],
        "scaling": {
          "instances": 1,
          "kind": "fixed"
        },
        "scheduling": {
          "placement": {
            "constraints": []
          }
        },
        "executorResources": {
          "cpus": 0.1,
          "mem": 32,
          "disk": 10
        },
        "fetch": []
      }
      

      The pod just fails and no log is generated. If I try yo check the logs of an instance, I get the message "Cannot Connect With The Server. You can also join us on our Slack channel or send us an email at help@dcos.io".

      The pod, as for now, only has one container because I'm experimenting with the concept. The configuration JSON file creates a working pod if I just erase the parts about the endpoints, so it's not a problem of the image or any other part of the configuration.

      So, is it a bug, an installation problem, a configuration problem...?

      I'm working on a DC/OS v1.10.2 cluster which comes with Marathon v1.5.2.

      Thanks beforehand!

        Attachments

          Activity

            People

            • Assignee:
              ivanchernetsky Ivan Chernetsky
              Reporter:
              unaipme unaipme
              Team:
              Orchestration Team
              Watchers:
              Alena Varkockova, Ivan Chernetsky, Till Toenshoff, unaipme
            • Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: