Configuring Health Checks for Your Marathon Applications in DC/OS
DC/OS was declared end of life October 31, 2021 and the content is no longer maintained
Description
Lab Overview
The Marathon container orchestration tool in DC/OS supports two types of checks to test the availability of applications: health checks and readiness checks. Health checks monitor the availability of an application's instances throughout the lifetime of the application. Readiness checks allow you to indicate when an application has finished initializing. In this Lab, you will see how to keep your applications up and running automatically by configuring health checks for your Marathon applications in DC/OS.
Lab Objectives
Upon completion of this Lab you will be able to:
- Add health and readiness checks to Marathon applications
- Describe the differences between health and readiness checks
- Diagnose issues related to health and readiness checks
Lab Prerequisites
You should be familiar with:
- Basic DC/OS concepts including master nodes, agents, services, tasks, and Marathon
- Working at the command-line in Linux
- AWS services to optionally understand the architecture of the pre-created DC/OS cluster
Lab Environment
Before completing the Lab instructions, the environment will look as follows:
After completing the Lab instructions, the environment should look similar to:
Updates
August 1st, 2021 - Resolved an issue preventing the DC/OS cluster from provisioning
March 29th, 2021 - Minor update to instructions for connecting to the NAT Instance
October 2nd, 2020 - Replaced CoreOS virtual machines (no longer available in AWS) with CentOS
January 10th, 2019 - Added a validation Lab Step to check the work you perform in the Lab