Viewing Service Instance Details
- Do one of the following:
- In the tab, if the cluster is displayed in full form, click ServiceName in a ClusterName table.
- In the tab, click ClusterName and then click ServiceName.
- Select .
- Click the Instances tab on the service's navigation bar. This shows all instances of all role types configured for the selected service.
You can also go directly to the Instances page to view instances of a specific role type by clicking one of the links under the Role Counts column. This will show only instances of the role type you selected.
The Instances page displays the results of the configuration validation checks it performs for all the role instances for this service.
The information on this page shows:
- The name of the role instance. Click the name to view the role status for that role.
- The host on which it is running. Click the hostname to view the host status details for the host.
- The rack assignment.
- The status. A single value summarizing the state and health of the role instance.
- Whether the role is currently in maintenance mode. If the role has been set into maintenance mode explicitly, you will see the following icon (). If it is in effective maintenance mode due to the service or its host having been set into maintenance mode, the icon will be this ().
- Whether the role is currently decommissioned.
You can sort or filter the Instances list by criteria in any of the displayed columns:
- Click the column header by which you want to sort. A small arrow indicates whether the sort is in ascending or descending order.
- Click the column header again to reverse the sort order.
- Filter - Type a property value in the Search box or select the value from the facets at the left of the page.
Role Instance Reference
The following tables contain reference information on the status, role state, and health columns for role instances.
|Started with outdated configuration||For a service, this indicates the service is running, but at least one of its roles is running with a configuration that does not match the current configuration settings in Cloudera Manager. For a role, this indicates a configuration change has been made that requires a restart, and that restart has not yet occurred. Click the indicator to display the Stale Configurations page.|
|Starting||The entity is starting up but is not yet running.|
|Stopping||The entity is stopping but has not stopped yet.|
|Stopped||The entity is stopped, as expected.|
|Down||The entity is not running, but it is expected to be running.|
|History not available||Cloudera Manager is in historical mode, and the entity does not have historical monitoring support. This is the case for services other than HDFS, MapReduce and HBase such as ZooKeeper, Oozie, and Hue.|
|None||The entity does not have a status. For example, it is not something that can be running and it cannot have health. Examples are the HDFS Balancer (which runs from the HDFS Rebalance action) or Gateway roles. The Start and Stop commands are not applicable to these instances.|
|Good health||The entity is running with good health. For a specific health test, the returned result is normal or within the acceptable range. For a role or service, this means all health tests for that role or service are Good.|
|Concerning health||The entity is running with concerning health. For a specific health test, the returned result indicates a potential problem. Typically this means the test result has gone above (or below) a configured Warning threshold. For a role or service, this means that at least one health test is Concerning.|
|Bad health||The entity is running with bad health. For a specific health test, the test failed, or the returned result indicates a serious problem. Typically this means the test result has gone above (or below) a configured Critical threshold. For a role or service, this means that at least one health test is Bad.|
|Disabled health||The entity is running, but all of its health tests are disabled.|
|Unknown health||The status of a service or role instance is unknown. This can occur for a number of reasons, such as the Service Monitor is not running, or connectivity to the Agent doing the health monitoring has been lost.|