Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

create unique task ID per task launch #94

Closed
wants to merge 7 commits into from
Closed

create unique task ID per task launch #94

wants to merge 7 commits into from

Commits on Mar 16, 2016

  1. Pass env vars to docker build

    @drewrobb @erikdw
    drewrobb authored and erikdw committed Mar 16, 2016
    Configuration menu
    Copy the full SHA
    01e0ee5 View commit details
    Browse the repository at this point in the history

  2. Update default mesos version to 0.27.0

    @drewrobb @erikdw
    drewrobb authored and erikdw committed Mar 16, 2016
    Configuration menu
    Copy the full SHA
    21486d6 View commit details
    Browse the repository at this point in the history

  3. Bug fix - Prevent losing logs due to incorrect shading 

          Issue: mesos#102
    @erikdw
    Karthick Duraisamy Soundararaj authored and erikdw committed Mar 16, 2016
    Configuration menu
    Copy the full SHA
    3c4a915 View commit details
    Browse the repository at this point in the history

  4. Migrate from 'log4j-over-slf4j' to 'slf4j'

    @erikdw
    Karthick Duraisamy Soundararaj authored and erikdw committed Mar 16, 2016
    Configuration menu
    Copy the full SHA
    6d3a7d4 View commit details
    Browse the repository at this point in the history

  5. create unique task ID per task launch 

    This is needed to avoid a problem with mesos-slave recovery resulting in LOST tasks.

i.e., we discovered that if you relaunch a topology's task onto the same worker slot (so there are 2 different instances with the same "task ID" that have run), then when the mesos-slave process is recovering, it terminates the task upon finding a "terminal" update in the recorded state of the task. The terminal state having been recorded the 1st time the task with that task ID stopped.

To solve this we ensure all task IDs are unique, by adding a milisecond-granularity timestamp onto the task IDs.
    @erikdw
    erikdw committed Mar 16, 2016
    Configuration menu
    Copy the full SHA
    ddde35d View commit details
    Browse the repository at this point in the history

  6. tweaks to use in-memory state for task assignments

    @erikdw
    erikdw committed Mar 16, 2016
    Configuration menu
    Copy the full SHA
    6c7bc0f View commit details
    Browse the repository at this point in the history

  7. Make TaskAssignments.AssignmentInfo serializable to avoid exception i… 

    …n mk-supervisor
    @erikdw
    erikdw committed Mar 16, 2016
    Configuration menu
    Copy the full SHA
    7f6b708 View commit details
    Browse the repository at this point in the history