Skip to content

Instantly share code, notes, and snippets.

@phstudy
Created May 13, 2014 09:03
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save phstudy/b3eef32c1e2b2a099d5f to your computer and use it in GitHub Desktop.
Save phstudy/b3eef32c1e2b2a099d5f to your computer and use it in GitHub Desktop.
cdh5_log
Inspector ran on all 4 hosts.
The following failures were observed in checking hostnames...
No errors were found while looking for conflicting init scripts.
No errors were found while checking /etc/hosts.
All hosts resolved localhost to 127.0.0.1.
All hosts checked resolved each other's hostnames correctly and in a timely manner.
Host clocks are approximately in sync (within ten minutes).
Host time zones are consistent across the cluster.
No users or groups are missing.
No conflicts detected between packages and parcels.
No kernel versions that are known to be bad are running.
Cloudera recommends setting /proc/sys/vm/swappiness to 0. Current setting is 60. Use the sysctl command to change this setting at runtime and edit /etc/sysctl.conf for this setting to be saved after a reboot. You may continue with installation, but you may run into issues with Cloudera Manager reporting that your hosts are unhealthy because they are swapping. The following hosts are affected:
hadoop4
hadoop1
hadoop3
hadoop2
No performance concerns with Transparent Huge Pages settings.
0 hosts are running CDH 4 and 4 hosts are running CDH5.
All checked hosts in each cluster are running the same version of components.
All managed hosts have consistent versions of Java.
All checked Cloudera Management Daemons versions are consistent with the server.
All checked Cloudera Management Agents versions are consistent with the server.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment