hands-on lab

Configuring Health Checks for Your Marathon Applications in DC/OS

Beginner
50m
50
This lab is currently under maintenance and unavailable. We are actively working to resolve this issue and we apologize for any inconvenience.

DC/OS was declared end of life October 31, 2021 and the content is no longer maintained

Get guided in a real environmentPractice with a step-by-step scenario in a real, provisioned environment.
Learn and validateUse validations to check your solutions every step of the way.
See resultsTrack your knowledge and monitor your progress.
Lab 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

About the author
Avatar
Logan Rakai, opens in a new tab
Lead Content Developer - Labs
Students
216,100
Labs
223
Courses
9
Learning paths
56

Logan has been involved in software development and research since 2007 and has been in the cloud since 2012. He is an AWS Certified DevOps Engineer - Professional, AWS Certified Solutions Architect - Professional, Microsoft Certified Azure Solutions Architect Expert, MCSE: Cloud Platform and Infrastructure, Google Cloud Certified Associate Cloud Engineer, Certified Kubernetes Security Specialist (CKS), Certified Kubernetes Administrator (CKA), Certified Kubernetes Application Developer (CKAD), and Certified OpenStack Administrator (COA). He earned his Ph.D. studying design automation and enjoys all things tech.

LinkedIn, Twitter, GitHub

Covered topics
Lab steps
Logging In to the Amazon Web Services Console
Understanding the DC/OS Cluster Architecture
Connecting to the DC/OS Cluster NAT Instance using SSH
Installing the DC/OS CLI on Linux
Adding a Health Check to a Marathon Application
Adding a Readiness Check to a Marathon Application
Validate AWS Lab