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.

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

Marathon should not re-use task ids for resident tasks #4819

Closed
unterstein opened this issue Dec 9, 2016 · 3 comments
Closed

Marathon should not re-use task ids for resident tasks #4819

unterstein opened this issue Dec 9, 2016 · 3 comments

Comments

@unterstein
Copy link
Contributor

unterstein commented Dec 9, 2016

In the current implementation, marathon re-uses task ids in case of resident tasks, see:

screenshot 2016-12-09 13 47 28

To avoid problems when running different tasks with the same task id, this behavior should be changed.

@timcharper
Copy link
Contributor

I noticed this as well. When I was writing my ceph-on-mesos framework I was directed to this and shied away: https://issues.apache.org/jira/browse/MESOS-2198

@marcomonaco marcomonaco added this to the Marathon 1.4 milestone Dec 15, 2016
@aquamatthias aquamatthias modified the milestones: Marathon 1.5, Marathon 1.4 Jan 2, 2017
@meichstedt
Copy link
Contributor

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-1772. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.

1 similar comment
@meichstedt
Copy link
Contributor

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-1772. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.

@mesosphere mesosphere locked and limited conversation to collaborators Mar 27, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants