0
0
Hadoopdata~10 mins

Monitoring with Ambari or Cloudera Manager in Hadoop - Interactive Code Practice

Choose your learning style9 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to start the Ambari server service.

Hadoop
sudo systemctl [1] ambari-server
Drag options to blanks, or click blank then click option'
Astop
Bstatus
Cstart
Drestart
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'stop' instead of 'start'.
Using 'status' which only shows service state.
2fill in blank
medium

Complete the command to check the status of Cloudera Manager agent.

Hadoop
sudo service cloudera-scm-agent [1]
Drag options to blanks, or click blank then click option'
Astart
Bstatus
Crestart
Dstop
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'start' or 'restart' instead of 'status'.
3fill in blank
hard

Fix the error in the command to restart Ambari agent.

Hadoop
sudo systemctl [1] ambari-agent
Drag options to blanks, or click blank then click option'
Arestart
Bstart
Cstop
Denable
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'start' alone does not restart if already running.
Using 'enable' only sets service to start on boot.
4fill in blank
hard

Fill both blanks to create a command that checks the Ambari server logs for errors.

Hadoop
sudo tail -n [1] /var/log/ambari-server/ambari-server.[2]
Drag options to blanks, or click blank then click option'
A100
Berror.log
Ccurrent
D50
Attempts:
3 left
💡 Hint
Common Mistakes
Using too few lines like 50 may miss errors.
Using 'error.log' is not the standard log file name.
5fill in blank
hard

Fill all three blanks to create a command that lists all running Cloudera Manager services and filters for 'Active'.

Hadoop
sudo systemctl list-units --type=[1] | grep [2] | grep [3]
Drag options to blanks, or click blank then click option'
Aservice
Bcloudera
CActive
Drunning
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'running' instead of 'Active' for filtering status.
Using wrong unit type like 'socket'.