[MESOS-1317] Add integration tests to enforce the semantics of a "strict" registry.

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.19.0
• Assignee: Benjamin Mahler
• Reporter: Benjamin Mahler
• Created: 06/May/14 21:54
• Updated: 13/May/14 17:48
• Resolved: 13/May/14 17:48

Description

There are a number registrar related items that we should add integration tests for, if possible:

• Recovered slaves that do not re-register are removed.
• Recovered slaves that re-register are not removed.
• --recovery_slave_removal_limit is enforced correctly.
• Non-strict: Recovered slave that does not re-register is removed, but no lost signals are sent.

• Reconciliation: unknown slave -> TASK_LOST
• Reconciliation: transitioning slave -> no response
• Reconciliation non-strict: unknown slave -> no response.

• killTask: unknown slave -> TASK_LOST
• killTask: transitioning slave -> no response

• Once slave is removed, slave cannot re-register with a failed over master.

Issue Links

• incorporates: MESOS-1319 Add recovery integration tests for a "strict" registry.
• incorporates: MESOS-1320 Add reconciliation integration tests for a "strict" registry.
• incorporates: MESOS-1321 Add killTask integration tests for a "strict" registry.
• incorporates: MESOS-1322 Add failover integration tests for a "strict" registry.