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

Port not re-offered after task dies

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Not A Problem
    • 0.23.0
    • None
    • scheduler driver
    • None

    Description

      I have a Mesos framework configured to accept a specific port for tasks (31150 in my case) and I have amount of tasks == amount of slaves so basically I have a task running on each slave on port 31150.

      I have Mesos slaves configured to offer 4000..7000,31000..32000 and I was successfully running all tasks until one of them threw an exception and died. The framework got the TASK_FAILED status update and I expected the task to be relaunched on the same machine and port but instead my framework says no offer has port 31150 in it. Is there a case when Mesos does not re-offer the port of dead task?

      Attachments

        Activity

          People

            Unassigned Unassigned
            serejja Serhey Novachenko
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: