Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upTasks to continue running after swarm crash #2352
Conversation
GordonTheTurtle
added
the
status/0-triage
label
Jun 15, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
Spritekin
Jun 15, 2016
@ezrasilvera @jimenez
Not sure why this throws errors. I think they are not related to the change. Can you do something please?
Spritekin
commented
Jun 15, 2016
|
@ezrasilvera @jimenez |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
@Spritekin the errors are unrelated. |
allencloud
added
the
area/mesos
label
Jul 11, 2016
Spritekin
referenced this pull request
Sep 28, 2016
Open
Swarm always trying to reschedule containers #2497
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Closing due to #2853 |
nishanttotla
closed this
May 30, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Spritekin commentedJun 15, 2016
By default, when a framework fails, Mesos will terminate any tasks started by a framework
The failovertimeout parameter allows the tasks to continue running for this number of seconds after the swarm manager dies. If not specified mesos will kill the tasks immediately (default behaviour). Mesos documentation recommends setting this value to 1 week time.
The frameworkid allows to specify a unique id. If Swarm manages to reconnect with the same task ID it had before the crash then mesos will reassigned the tasks to it. The ID must follow the mesos format for IDs (i.e. b2853a78-7cba-455a-99c7-d73bb5cbda95-0024). Refer to mesos for ID formats.
Signed-off-by: Guillermo Rodriguez [email protected]