sbt test
sbt integration:test
Details
- Reviewers
jeschkies zen-dog jenkins ichernetsky kensipe - Commits
- rMARATHONd37aa8ed8266: Change unreachableStrategy to be able to start instant replacement tasks
rMARATHON60eccad14a58: Change unreachableStrategy to be able to start instant replacement tasks (#5459)
rMARATHON02b18924ebfb: Change unreachableStrategy to be able to start instant replacement tasks
rMARATHON95273f2e9bf3: fixed test
rMARATHON68f4c38db07d: docs
rMARATHONc14f3cb80e85: [WIP] Change unreachableStrategy to be able to start instant replacement tasks
rMARATHON1dff7962d8f7: adapted validation
rMARATHONd103c6c4938a: Change unreachableStrategy to be able to start instant replacement tasks
rMARATHONc9aeb3e48d5f: docs
rMARATHON47e077ff7761: [WIP] Change unreachableStrategy to be able to start instant replacement tasks
rMARATHON1f979957c9fb: wait for task to be running - JIRA Issues
- JIRA MARATHON-7859 Allow immediate replacement of unreachable instances
Diff Detail
- Repository
- rMARATHON marathon
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Thanks!
src/test/scala/mesosphere/marathon/integration/TaskUnreachableIntegrationTest.scala | ||
---|---|---|
90 | Hm, you could add a test with immediate expunge as well ;). |
IMO this requires more context... we (the developers) have been dealing with this and understand what is happening... however this a change log intended for marathon users. It is highly unlikely they know or understand unreachable (vs lost etc).
at a min add a link to: https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto#L2053
clarify that this isn't task_lost but TASK_UNREACHABLE. under this condition with default configurations it takes 75 seconds to receive indication from mesos that the task unreachable.
(I did read below and realize you have some details around 75 sec delay... it needs context for the standard reader.