******* MESOS SLAVE METRICS **********
Slaves active : 41
Slaves connected : 41
Slaves disconnected: 0
Slaves inactive: 0
Troubleshooting information
●
If the system indicates that the
mesos-slave
process is running, but it is not possible to schedule jobs,
execute the following commands as root on each of the agent/slave node:
#
systemctl stop urika-mesos-slave
#
rm -vf /var/log/mesos/agent/meta/slaves/latest
#
systemctl start urika-mesos-slave
●
If the Mesos UI displays orphaned Mesos tasks, refer to
Diagnose and Troubleshoot Orphaned Mesos Tasks
on page 258 to debug the issue.
●
Mesos logs are located at
/var/log/mesos
, whereas log files of Mesos framework are located
under
/var/log/mesos/agent/slaves/
on the node(s) the service runs on.
For more information about Mesos, visit
5.2.1
Access the Apache Mesos Web UI
Prerequisites
●
Before performing this procedure use the
urika-state
script to verify that the Mesos service is running.
●
Check the service mode by executing
urika-service-mode
to ensure that the system is running in the
service mode required for Mesos to run.
About this task
The Mesos web UI can be used to monitor components of the Mesos cluster, such as the Mesos slaves,
aggregated resources and frameworks.
Do not launch applications through Mesos directly because all the frameworks are pre-configured on Urika-GX.
Only a few frameworks (Spark and Marathon) are pre-configured to authenticate with Mesos.
Procedure
1. Access the Mesos UI using once of the following mechanisms:
●
Point a browse at the Urika-GX Applications Interface at:
http://
hostname
-login1
and then select
the Mesos icon. This is the recommended approach.
●
Point a browser at
http://
hostname
-login1:5050
or
http://
hostname
-login2:5050
2. Enter a username and the Mesos secret in the Authentication Required pop up's UserName and
Password fields respectively.
The Mesos secret can be retrieved from the
/security/secrets/
userName
.mesos
file, which is located
on the SMW.
Resource Management
S3016
128
