- A Cloud Guru
Moving Your Nomad Job from One Node to Another
In Nomad, it's important to be able to control the nodes that run your jobs. You have been provided with a Nomad cluster that has two client nodes. The tasks you will perform in this hands-on lab will be performed on the provided Nomad server, which has been configured with one server agent and two client agents. Docker has been installed so that Nomad is ready to run jobs. In this lab, you will be tasked with creating and running a Nomad job. Then you will take the node running that job out of use by draining it. This will demonstrate that jobs running on a node that gets shut down will migrate to another node.
Table of Contents
Log in to the Provided Nomad Server
Log into the server as "cloud_user" with the provided password to perform the tasks.
Create a Nomad Job and Submit it to Run
Using Nomad commands, create a default Nomad job. Once the job has been created, submit it to run. Only one allocation should start.
Check Which Node is Running the Job's Allocation
Once the job is marked as healthy, use a Nomad command to drain that client node. Your job should move from that node and start up again on the other one.
Check if the Node is Now Ineligible
The node that was shut down should now be marked as ineligible to receive new jobs. It should, however, stay in ready status. The job you created should still be running but on the second client node.
What's a lab?
Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.