Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-3814

Add checks to make sure isolators and the launcher are compatible.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Accepted
    • Major
    • Resolution: Unresolved
    • 0.26.0
    • None
    • None
    • 2

    Description

      There's a recent change regarding the picking of which launcher (Linux or Posix) to use
      https://reviews.apache.org/r/39604

      In our environment, cgroups are not auto-mounted after reboot. We rely on Mesos itself to mount all relevant cgroups hierachies.

      After the reboot, the above patch detects that 'freezer' hierarchy is not mounted, therefore, decided to use the Posix launcher (if --launcher is not specified explictly).

      Port mapping isolator requires network namespace to be created for each container (thus requires Linux launcher). But we don't have a check to verify that launcher and isolators are compatible.

      Slave thus starts fine and task failed with weird error like:

      Collect failed: Failed to create the ingress qdisc on mesos61099: Link 'mesos61099' is not found.
      

      It does take us quite a few time to figure out the root cause.

      Attachments

        Activity

          People

            hartem Artem Harutyunyan
            jieyu Jie Yu
            Jie Yu Jie Yu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: