34
Cloudera Manager Introduction

Cloudera Manager Intro

  • Upload
    geeyes1

  • View
    217

  • Download
    1

Embed Size (px)

DESCRIPTION

Cloudera Manager Intro

Citation preview

Page 1: Cloudera Manager Intro

Cloudera Manager Introduction

Page 2: Cloudera Manager Intro

Important Notice

(c) 2010-2013 Cloudera, Inc. All rights reserved.

Cloudera, the Cloudera logo, Cloudera Impala, and any other product or service names orslogans contained in this document are trademarks of Cloudera and its suppliers or licensors,and may not be copied, imitated or used, in whole or in part, without the prior writtenpermission of Cloudera or the applicable trademark holder.

Hadoop and the Hadoop elephant logo are trademarks of the Apache Software Foundation.All other trademarks, registered trademarks, product names and company names or logosmentioned in this document are the property of their respective owners. Reference to anyproducts, services, processes or other information, by trade name, trademark, manufacturer,supplier or otherwise does not constitute or imply endorsement, sponsorship orrecommendation thereof by us.

Complying with all applicable copyright laws is the responsibility of the user. Without limitingthe rights under copyright, no part of this document may be reproduced, stored in orintroduced into a retrieval system, or transmitted in any form or by any means (electronic,mechanical, photocopying, recording, or otherwise), or for any purpose, without the expresswritten permission of Cloudera.

Cloudera may have patents, patent applications, trademarks, copyrights, or other intellectualproperty rights covering subject matter in this document. Except as expressly provided inany written license agreement from Cloudera, the furnishing of this document does notgive you any license to these patents, trademarks copyrights, or other intellectual property.

The information in this document is subject to change without notice. Cloudera shall notbe liable for any damages resulting from technical errors or omissions which may be presentin this document, or from use of this document.

Cloudera, Inc.1001 Page Mill Road, Building 2Palo Alto, CA [email protected]: 1-888-789-1488Intl: 1-650-362-0488www.cloudera.com

Release Information

Version: 4.7.2

Date: September 19, 2013

Page 3: Cloudera Manager Intro

Table of Contents

About This Guide........................................................................................................5

Cloudera Manager Primer.........................................................................................7Terminology..................................................................................................................................................7Architecture..................................................................................................................................................8State Management......................................................................................................................................9Configuration Management.....................................................................................................................10Process Management...............................................................................................................................12Software Distribution Management........................................................................................................12

Advantages of Parcels...........................................................................................................................................12Parcel Life Cycle......................................................................................................................................................13Cloudera Manager Capabilities Enabled by Parcels............................................................................................14

Management Services...............................................................................................................................15

Cloudera Manager Admin Console.........................................................................17Starting and Logging into the Admin Console........................................................................................19Home Page.................................................................................................................................................19

Cloudera Manager API.............................................................................................23Using the Cloudera Manager Java API for Cluster Automation............................................................23

Cluster Automation Use Cases.............................................................................................................................23Java API Examples..................................................................................................................................................24

Cloudera Manager Guides.......................................................................................27

Cloudera Manager Frequently Asked Questions .................................................29General Questions.....................................................................................................................................29Using Cloudera Manager...........................................................................................................................31

Getting Help and Support........................................................................................33Community Support..................................................................................................................................33Cloudera Enterprise Support....................................................................................................................33

Page 4: Cloudera Manager Intro

Get Announcements about New CDH and Cloudera Manager Releases............................................33Report Issues.............................................................................................................................................33

Page 5: Cloudera Manager Intro

About This Guide

This guide provides a comprehensive introduction to Cloudera Manager.

• Cloudera Manager Primer on page 7• Cloudera Manager Admin Console on page 17• Cloudera Manager API on page 23• Cloudera Manager Guides on page 27• Cloudera Manager Frequently Asked Questions on page 29• Getting Help and Support on page 33

Cloudera Manager Introduction | 5

About This Guide

Page 6: Cloudera Manager Intro
Page 7: Cloudera Manager Intro

Cloudera Manager Primer

This primer introduces the basic concepts, structure, and functions of Cloudera Manager. It covers the followingtopics:

• Terminology on page 7• Architecture on page 8• State Management on page 9• Configuration Management on page 10• Process Management on page 12• Software Distribution Management on page 12• Management Services on page 15

TerminologyTo effectively use Cloudera Manager, you should first understand its terminology. The relationship between theterms is illustrated below and their definitions follow:

Some of the terms, such as cluster and service, will be used without further explanation. Others, such as gatewayand role group, are expanded upon in later sections.

• deployment - A configuration of Cloudera Manager and all the services and hosts it manages.• cluster - A logical entity that contains a set of hosts, a single version of CDH installed on the hosts, and the

service and role instances running on the hosts. A host may only belong to one cluster.• host - A logical or physical machine that runs role instances.• rack - A physical entity that contains a set of hosts typically served by the same switch.• service - A category of functionality within the Hadoop ecosystem. Sometimes referred to as a service type.

For example: HDFS, MapReduce.• service instance - An instance of a service running on a cluster. A service instance spans many role instances.

For example: HDFS-1 and MapReduce-1.• role - A category of functionality within a service. For example, the HDFS service has the following roles:

NameNode, SecondaryNameNode, DataNode, and Balancer. Sometimes referred to as a role type.

Cloudera Manager Introduction | 7

Cloudera Manager Primer

Page 8: Cloudera Manager Intro

• role instance - An instance of a role, assigned to a host. It typically maps to a Unix process. For example:NameNode-h11 and DataNode-h11.

• role group - A set of configuration properties for a role and set of role instances.• host template - A set of role groups. When a template is applied to a host, a role instance from each role

group is created and assigned to that host.• gateway - A role that designates a host that should receive a client configuration for a service when the host

does not have any roles for that service running on it.

It's also helpful to always remember this basic principle: Whereas in traditional environments multiple servicesrun on one host, in Hadoop — and other distributed systems — a service runs on many hosts.

Note: In programming languages, the term "string" may indicate either a type (java.lang.String)or an instance of that type ("hi there"). A common point of confusion is the type-instance nature of"service" and "role". Cloudera Manager and this primer sometimes uses the same term for type andinstance.

For example, the sentence before this note uses the word "services" and "service", but is actuallyreferring to service instances. Likewise the Cloudera Manager Admin Console "Services" screen displaysservice instances. When it's necessary to distinguish between types and instances, the word "type"is appended to indicate a type and the word "instance" is appended to explicitly indicate an instance.

ArchitectureAs depicted below, the heart of Cloudera Manager is the Cloudera Manager Server. The Server hosts the AdminConsole Web Server and the application logic. It is responsible for installing software, configuring, starting, andstopping services, and managing the cluster on which the services run.

The Cloudera Manager Server works with several other components:

• Agent - installed on every host. It is responsible for starting and stopping processes, unpacking configurations,triggering installations, and monitoring the host.

• Database - stores configuration and monitoring information. There are typically multiple logical databasesrunning across one or more database servers. For example, the Cloudera Manager Server and the monitoringdaemons use different logical databases.

• Cloudera Repository - repository of software for distribution by Cloudera Manager.• Clients provide an interface for interacting with the server.

8 | Cloudera Manager Introduction

Cloudera Manager Primer

Page 9: Cloudera Manager Intro

Admin Console - Web-based UI with which administrators manage clusters and Cloudera Manager.–– API - API with which developers create custom Cloudera Manager applications.

Heartbeating

Heartbeats are a primary communication mechanism in Cloudera Manager. By default the agents send heartbeatsevery 15 seconds to the Cloudera Manager Server. However, to reduce user latency the frequency is increasedwhen state is changing.

During the heartbeat exchange the agent notifies the Cloudera Manager Server the actions it is performing. Inturn the Cloudera Manager Server responds with the actions the agent should be performing. Both the agentand the Cloudera Manager Server end up doing some reconciliation. For example, if you start a service via theUI, the agent attempts to start the relevant processes; if a process fails to start, the server marks the startcommand as having failed.

State ManagementThe Cloudera Manager Server maintains the state of the cluster. This state can be divided into two categories:"model" and "runtime", both of which are stored in the Cloudera Manager Server database.

Cloudera Manager models the Hadoop stack: its roles, configurations, and inter-dependencies. Model statecaptures what is supposed to run where, and with what configurations. That a cluster contains 17 hosts, eachof which is supposed to run a DataNode, is model state. You interact with the model through the ClouderaManager configuration screens (and operations like "Add Service").

Runtime state is what processes are running where, and what commands (for example, rebalance HDFS orexecute a Backup/Disaster Recovery schedule or rolling restart or stop) are currently being executed. The runtimestate includes the exact configuration files needed to run a process. In fact, when you press "Start" in ClouderaManager Admin Console, the server gathers up all the configuration for the relevant services and roles, validatesit, generates the configuration files, and stores them in the database.

When you update a configuration (for example, the Hue Server web port), you've updated the model state.However, if Hue is running while you do this, it's still using the old port. When this kind of mismatch occurs, therole is marked as having an "outdated configuration". To resynchronize, you restart the role (which triggers theconfiguration re-generation and process restart).

While Cloudera Manager models all of the reasonable configurations, inevitably, there are some corner casesthat require special handling. To allow you to workaround, for example, some bug (or, perhaps, to exploreunsupported options), Cloudera Manager supports a "safety valve" mechanism that lets you plug in directly tothe configuration files. (The analogy stems from the idea that a safety valve "releases pressure" if the modeldoesn't hold up to a real-world use case.)

Cloudera Manager Introduction | 9

Cloudera Manager Primer

Page 10: Cloudera Manager Intro

Configuration ManagementCloudera Manager defines configuration at several levels:

• The service level may define configurations that apply to the entire service instance, such as an HDFS service'sdefault replication factor (dfs.replication).

• The role group level may define configurations that apply to the member roles, such as the DataNodes' handlercount (dfs.datanode.handler.count). This can be set differently for different groups of DataNodes.For example, DataNodes running on more capable hardware may have more handlers.

• The role instance level may override configurations that it inherits from its role group. This should be usedsparingly, because it easily leads to configuration divergence within the role group. One example usage is totemporarily enable debug logging in a specific role instance to troubleshoot an issue.

• Hosts have configurations related to monitoring, software management, and resource management.• Cloudera Manager itself has configurations related to its own administrative operations.

Role Groups

It is possible to set configuration at the service instance (for example, HDFS-1), role (for example, all DataNodes),or role instance (for example, the DataNode on host17). An individual role inherits the configurations set at theservice and role-type levels. Configurations made at the role level override those from the role-type level. Whilethis approach offers flexibility when configuring clusters, it is tedious to configure subsets of roles in the sameway.

Cloudera Manager supports role groups, a mechanism for assigning configurations to a group. The members ofthose groups then inherit those configurations. For example, in a cluster with heterogeneous hardware, aDataNode role group can be created for each host type and the DataNodes running on those hosts can beassigned to their corresponding role group. That makes it possible to set the configuration for all the DataNodesrunning on the same hardware by modifying the configuration of one role group.

In addition to making it easy to manage the configuration of subsets of roles, role groups also make it possibleto maintain different configurations for experimentation or managing shared clusters for different users and/orworkloads.

Host Templates

In typical environments, sets of hosts have the same hardware and the same set of services running on them.A host template defines a set of role groups (at most one of each type) in a cluster and provides two mainbenefits:

• Adding new hosts to clusters easily - multiple hosts can have roles from different services created, configured,and started in a single operation.

• Altering the configuration of roles from different services on a set of hosts easily - which is useful for quicklyswitching the configuration of an entire cluster to accommodate different workloads or users.

Server and Client Configuration

Administrators are sometimes surprised that modifying /etc/hadoop/conf and then restarting HDFS has noeffect. That is because service instances started by Cloudera Manager do not read configurations from thedefault locations. To use HDFS as an example, when not managed by Cloudera Manager, there would usuallybe one HDFS configuration per host, located at /etc/hadoop/conf/hdfs-site.xml. Server-side daemons andclients running on the same host would all use that same configuration.

Cloudera Manager distinguishes between server and client configuration. In the case of HDFS, the file/etc/hadoop/conf/hdfs-site.xml contains only configuration relevant to an HDFS client. That is, by default,if you run a program that needs to communicate with Hadoop, it will get the addresses of the NameNode and

10 | Cloudera Manager Introduction

Cloudera Manager Primer

Page 11: Cloudera Manager Intro

JobTracker, and other important configurations, from that directory. A similar approach is taken for/etc/hbase/conf and /etc/hive/conf.

The HDFS server-side daemons (for example, NameNode and DataNode) obtain their configurations from aprivate per-process directory, under /var/run/cloudera-scm-agent/process/unique-process-name. Givingeach process its own private execution and configuration environment allows us to control each processindependently, which is crucial for some of the more esoteric configuration scenarios that show up. Here arethe contents of an example 879-hdfs-NAMENODE process directory:

$ tree -a /var/run/cloudera-scm-agent/process/879-hdfs-NAMENODE//var/run/cloudera-scm-agent/process/879-hdfs-NAMENODE/├── cloudera_manager_agent_fencer.py├── cloudera_manager_agent_fencer_secret_key.txt├── cloudera-monitor.properties├── core-site.xml├── dfs_hosts_allow.txt├── dfs_hosts_exclude.txt├── event-filter-rules.json├── hadoop-metrics2.properties├── hdfs.keytab├── hdfs-site.xml├── log4j.properties├── logs│ ├── stderr.log│ └── stdout.log├── topology.map└── topology.py

There are several advantages to distinguishing between server and client configuration:

• Sensitive information in the server-side configuration, such as the password for the Hive metastore RDBMS,is not exposed to the clients.

• A service that depends on another service may deploy with customized configuration. For example, to getgood HDFS read performance, Cloudera Impala needs a specialized version of the HDFS client configuration,which may be harmful to a generic client. This is achieved by separating the HDFS configuration for theImpala daemons (stored in the per-process directory mentioned above) from that of the generic client(/etc/hadoop/conf).

• Client configuration files are much smaller and more readable. This also avoids confusing non-administratorHadoop users with irrelevant server-side properties.

Deploying Client Configurations and Gateways

A client configuration is a ZIP file that contain the relevant configuration files with the settings for a service.Each zip file contains the set of configuration files needed by the service. For example, the MapReduce clientconfiguration zip file contains copies of core-site.xml, hadoop-env.sh, hdfs-site.xml, log4j.properties, and mapred-site.xml. Cloudera Manager supports a "Client Configuration URLs" action to distribute the clientconfiguration file to users outside the cluster.

Cloudera Manager can deploy client configurations within the cluster; each applicable service has a "DeployClient Configuration" action. This action does not necessarily deploy the client configuration to the entire cluster;it only deploys the client configuration to all the hosts that this service has been assigned to. For example,suppose a cluster has 10 nodes, and a MapReduce service is running on hosts 1-9. When you use ClouderaManager to deploy the MapReduce client configuration, host 10 will not get a client configuration, because theMapReduce service has no role assigned to it. This design is intentional to avoid deploying conflicting clientconfigurations from multiple services.

To deploy a client configuration to a host that does not have a role assigned to it you use a gateway. A gatewayis a marker to convey that a service includes a particular host. Unlike all other roles it has no associated process.In the preceding example, to deploy the MapReduce client configuration to host 10, you assign a MapReducegateway role to that host.

Cloudera Manager Introduction | 11

Cloudera Manager Primer

Page 12: Cloudera Manager Intro

Process ManagementIn a non-Cloudera Manager managed cluster, you most likely start a role instance using an init script, for example,service hadoop-hdfs-datanode start. Cloudera Manager does not use init scripts for the daemons itmanages; in a Cloudera Manager managed cluster, starting and stopping services using init scripts will not work.

In a Cloudera Manager managed cluster you can only start or stop services via Cloudera Manager. ClouderaManager uses an open source supervisor called supervisord that takes care of redirecting log files, notifying ofprocess failure, setting the effective user ID of the calling process to the right user, and so forth. Cloudera Managersupports automatically restarting a crashed process. It will also flag a role instance with a bad state if it crashesrepeatedly right after start up.

It is worth noting that stopping Cloudera Manager and the Cloudera Manager agents will not bring down yourcluster; any running instances will keep running.

One of the agent's main responsibilities is to start and stop processes. When the agent detects a new processfrom the heartbeat, the agent creates a directory for it in /var/run/cloudera-scm-agent and unpacks theconfiguration. These actions reflect an important point: a Cloudera Manager process never travels alone. In otherwords, a process is more than just the arguments to exec() — it also includes configuration files, directoriesthat need to be created, and other information.

The agent itself is started by init.d at start-up. It, in turn, contacts the server and figures out what processesshould be running. The agent is monitored as part of Cloudera Manager's host monitoring: if the agent stopsheartbeating, the host will be marked as having bad health.

Software Distribution ManagementA major function of Cloudera Manager is to distribute and activate software in your cluster. Cloudera Managersupports two software distribution formats: packages and parcels.

A package is a distribution format that contains compiled code and meta-information such as a packagedescription, version, and dependencies. Package management systems evaluate this meta-information to allowpackage searches, perform upgrades to a newer version, and ensure that all dependencies of a package arefulfilled. Cloudera Manager uses the native "system package manager" for each supported OS.

A parcel is a binary distribution format available since Cloudera Manager 4.5. A parcel is simply a tarball containingthe program files, along with additional metadata used by Cloudera Manager. There are a few notable differencesbetween parcels and packages:

• Parcels are self-contained and installed in a versioned directory. This means that multiple versions of a givenparcel can be installed "side-by-side". You can then designate one of these installed versions as the "active"one. With traditional packages, only one package can be installed at a time so there's no distinction betweenwhat's "installed" and what's "active".

• Parcels can be installed at any location in the filesystem.

Advantages of Parcels

As a consequence of their unique properties, parcels offer a number of advantages over packages:

• CDH is distributed as a single object - In contrast to having a separate package for each part of CDH, whenusing parcels there is just a single object to install. This is especially useful when managing a cluster thatisn't connected to the Internet.

• Internal consistency - All CDH components are matched so there isn't a danger of different parts comingfrom different versions of CDH.

12 | Cloudera Manager Introduction

Cloudera Manager Primer

Page 13: Cloudera Manager Intro

• Installation outside of /usr - In some environments, Hadoop administrators do not have privileges to installsystem packages. In the past, these administrators had to fall back to CDH tarballs, which deprived them ofa lot of infrastructure that packages provide. With parcels, administrators can install to /opt or anywhereelse without having to step through all the additional manual steps of regular tarballs.

• Installation of CDH without sudo - Parcel installation is handled by the Cloudera Manager Agent running asroot so it's possible to install CDH without needing sudo.

• Decouples distribution from activation - Due to side-by-side install capabilities, it is possible to stage a newversion of CDH across the cluster in advance of switching over to it. This allows the longest running part ofan upgrade to be done ahead of time without affecting cluster operations, consequently reducing the downtimeassociated with upgrade.

• Rolling upgrades - These are only possible with parcels, due to their side-by-side nature. Traditional packagesrequire shutting down the old process, upgrading the package, and then starting the new process. This canbe hard to recover from in the event of errors and requires extensive integration with the package managementsystem to function seamlessly. With the new version staged side-by-side, switching to a new minor versionis simply a matter of changing which version of CDH is used when restarting each process. It then becomespractical to do upgrades with rolling restarts, where service roles are restarted in the right order to switchover to the new version with minimal service interruption. Note that major version upgrades (for example,CDH3 to CDH4) require full service restarts due to the substantial changes between the versions.

• Easy downgrades - With the old version still available, reverting back to it can be as simple as upgrading.Note that some CDH components may require explicit additional steps due to things like schema upgrades.

Parcel Life Cycle

The life cycle of a parcel is depicted below and the descriptions of the phases follows:

• Download - When a parcel is available in the Cloudera repository, Cloudera Manager can download it to theCloudera Manager Server machine.

• Distribution - Once the Cloudera Manager Server has downloaded the parcel, it can distribute it to all thehosts in the cluster. This process can be tuned in terms of how many hosts receive the parcel at the sametime and the total aggregate bandwidth used for the process.

Cloudera Manager Introduction | 13

Cloudera Manager Primer

Page 14: Cloudera Manager Intro

• Activation - Once a parcel is distributed, you can activate it. Once activated, the parcel will be used for anyprocesses that are subsequently started or restarted.

• Deactivation - Similarly, a parcel can be deactivated (and will automatically be deactivated if another one isactivated).

• Removal - This is the reverse of distribution. A parcel that has been deactivated and is not serving any currentprocesses is eligible for removal from the hosts in the cluster.

• Deletion - Once removed from the cluster, the parcel can be deleted from the Cloudera Manager Server, whichcompletes the life cycle of the parcel.

For example, the following screenshot:

shows:

• One activated CDH and one activated Impala parcel• One CDH parcel being downloaded• One CDH parcel being distributed• One CDH parcel available for download

Cloudera Manager Capabilities Enabled by Parcels

In addition to the advantages of parcels described in the preceding section, parcels enable capabilities deliveredby Cloudera Manager:

• Upgrade management - Cloudera Manager can fully manage all the steps involved in a CDH version upgrade.In contrast, with packages, Cloudera Manager can only help with initial installation.

• Distributing additional components - Parcels are not limited to CDH. Cloudera Impala, Cloudera Search, andLZO are also available.

• Compatibility with other distribution tools - If there are specific reasons to use other tools for downloadand/or distribution, you can do so, and Cloudera Manager will work alongside your other tools. For example,you can handle distribution with something like Puppet. Or, if you want to download the parcel to ClouderaManager Server manually (perhaps because your cluster has no Internet connectivity) and then have ClouderaManager distribute the parcel to the cluster, you can do that too.

14 | Cloudera Manager Introduction

Cloudera Manager Primer

Page 15: Cloudera Manager Intro

Management ServicesCloudera Manager manages its helper management services: Service Monitor, Activity Monitor, Host Monitor,Event Server, Reports Manager, and Alert Publisher. Cloudera Manager manages each separately (as opposedto rolling them all in as part of the Cloudera Manager Server) for scalability (for example, on large deploymentsit's useful to put the monitors on their own hosts) and isolation.

Metric Collection and Display

To perform its monitoring, Cloudera Manager collects metrics. A metric is a numeric value, associated with aname (for example, "CPU seconds"), an entity it applies to ("host17"), and a timestamp. Most metric collection isperformed by the agent. The agent communicates with a supervised process, requests the metrics, and forwardsthem to the service monitor. In most cases, this is done once per minute.

A few special metrics are collected by the Service Monitor. For example, the Service Monitor hosts an HDFScanary, which tries to write, read, and delete a file from HDFS at regular intervals, and measure whether itsucceeded, and how long it took. Once metrics are received, they're aggregated and stored.

Using the Charts page in Cloudera Manager, you can query and explore the metrics being collected. Charts displaytime series, which are streams of metric data points for a specific entity. Each metric data point contains atimestamp and the value of that metric at that timestamp.

Some metrics (for example, total_cpu_seconds) are counters, and the appropriate way to query them is totake their rate over time, which is why a lot of metrics queries contain the dt0 function. For example,dt0(total_cpu_seconds). (The dt0 syntax is intended to remind you of derivatives. The 0 indicates thatthe rate of a monotonically increasing counter should never have negative rates.)

Health Tests

The Service Monitor continually evaluates "health tests" for every entity in the system. For example, a simplehealth test is whether there's enough disk space in every NameNode data directory. A more complicated healthtest may evaluate when the last checkpoint for HDFS was compared to a threshold or whether a DataNode isconnected to a NameNode. Some of these health tests also aggregate other health tests: in a distributed systemlike HDFS, it's normal to have a few DataNodes down (assuming you've got dozens of machines), so we allowfor setting thresholds on what percentage of nodes should color the entire service down.

Health tests can assume three values: Good, Concerning, and Bad. A test returns Concerning health if the testfalls below a warning threshold. A test returns Bad if the test falls below a critical threshold. The overall healthof a service or role instance is a roll-up of its health checks. If any health test is Concerning (but none are Bad)the role's or service's health is Concerning; if any health test is Bad, the service's or role's health is Bad.

One common question is whether monitoring can be separated from configuration. One of the goals for monitoringis to enable it without needing to do additional configuration and installing additional tools (for example, Nagios).By having a deep model of the configuration, Cloudera Manager is able to know which directories to monitor,which ports to use, and what credentials to use for those ports. This tight coupling means that, when you installCloudera Standard (the free version of the Cloudera platform), all the monitoring is enabled.

Events and Alerts

An event is a record that something of interest has occurred: a service's health has changed state, a log message(of the appropriate severity) has been logged, and so on. For example, when a health test is Bad, an event isusually created.

An alert is event that is considered especially noteworthy and is triggered by a selected event. Alerts appear

with a red badge when you view events in a list. You can configure the Alert Publisher to send alertnotifications by email or via SNMP trap to a trap receiver such as HP OpenView.

Cloudera Manager Introduction | 15

Cloudera Manager Primer

Page 16: Cloudera Manager Intro
Page 17: Cloudera Manager Intro

Cloudera Manager Admin Console

Cloudera Manager Admin Console is the web-based UI that you use to configure, manage, and monitor CDH.Cloudera Manager Admin Console supports the following web browsers:

• Firefox 11 or later• Google Chrome• Internet Explorer 9• Safari 5 or later

If there are no services configured when you log into the Cloudera Manager Admin Console, the Cloudera Managerinstallation wizard displays. If services have been configured, the Cloudera Manager top navigation bar:

and Home page display. The Home page is the central point from which you can view the status of your cluster.In addition to a link to the Home page, the Cloudera Manager Admin Console top navigation bar provides thefollowing features:

• Services - Displays All Services, individual services, and Cloudera Management Services. In these pages youcan:

– View the status and other details of a service instance or the role instances associated with the service– Make configuration changes to a service instance, a role, or a specific role instance– Add and delete a service or role– Stop, start, or restart a service or role.– View the commands that have been run for a service or a role– View an audit event history for a service or role instance– Deploy client configurations– Decommission and recommission role instances

You can also perform actions unique to a specific type of service, for example:

• Enable HDFS High Availability or NameNode Federation• Run the Balancer (HDFS)

• Hosts - Displays the hosts managed by Cloudera Manager. In this page you can:

– View the status and a variety of detail metrics about individual hosts– Make configuration changes for host monitoring– View all the processes running on a host, with status, access to logs and so on– Run the Host Inspector– Add and delete hosts– Create and manage host templates– Manage (download, distribute and activate) parcels.– Decommission and recommission hosts– Make rack assignments– Run the host upgrade wizard

• Activities - Displays information about processes - MapReduce jobs and Cloudera Impala queries - runningon your cluster.

• Diagnose - Provides tools for diagnosing problems. The subpages are:

Cloudera Manager Introduction | 17

Cloudera Manager Admin Console

Page 18: Cloudera Manager Intro

Logs - Supports searching logs by service, role, host, and search phrase as well as log level (severity).–– Events - Supports searching for and displaying events and alerts that have occurred.– Server Log -Displays the Cloudera Manager Server log.

• Audits - Supports list and filtering audit events across clusters.• Charts - Supports searching for metrics of interest, displaying them as charts, and displaying personalized

chart views.• Reports - Supports creating reports about the HDFS and MapReduce usage, browsing files, and managing

quotas for HDFS directories.• Administration - Supports actions to administer Cloudera Manager:

– Settings - Configuring Cloudera Manager.– Import (Deprecated) - Importing a Cloudera Manager deployment.– Alerts - Displays when alerts will be generated, supports configuring alert recipients and sending test

alert email.– Users - Managing Cloudera Manager users.– Kerberos - Generating Kerberos credentials and inspecting hosts.– License - Managing Cloudera licenses.– Language - Setting the language used for the content of activity events, health events, and alert email

messages.– Peers - Connecting multiple instances of Cloudera Manager

• Indicators

–Parcel Indicator - indicates how many parcels containing new versions of your software are available.

–Running Commands Indicator - indicates how many commands are currently running.

• Search - Supports searching by service, role or host name. You can enter a partial name and it will searchfor all entities that match.

• Support - Displays various support actions. The subcommands are:

– Send Diagnostic Data - Sends data to Cloudera Support to support troubleshooting.– Support Portal (Cloudera Enterprise) - Displays the Cloudera Support portal.– Mailing List (Cloudera Standard) - Displays the Cloudera Manager Users list.– Scheduled Diagnostics: Weekly - Displays the Administration > Settings page where you can configure

the frequency of automatically collecting diagnostic data and sending to Cloudera support.– The following links open the latest documentation on the Cloudera web site:

– Help– Installation Guide– API Documentation– Release Notes

– About - Displays version number and build details of Cloudera Manager and the current date and timestamp of the Cloudera Manager server.

• Logged-in User Menu - Displays the currently logged-in user. For example, if you are logged in as admin this

menu will be . The subcommands are:

– Logout– Change Password - Displays the Change Password page.

18 | Cloudera Manager Introduction

Cloudera Manager Admin Console

Page 19: Cloudera Manager Intro

Starting and Logging into the Admin Console1. In a web browser, type the following URL:

http(s)://<Server host>:<port>

where: <Server host> is the name or IP address of the host machine where the Cloudera Manager Serveris installed. <port> is the port configured for the Cloudera Manager Server. The default port is 7180.

2. Log into the Cloudera Manager Admin Console. The admin user credentials are:

Username: adminPassword: admin

Note: For security, change the password for the default admin user account as soon as possible. Youcan also add user accounts and selectively assign admin privileges to them as necessary. Forinstructions, see the Changing the Password for an Account.

Home PageWhen you start the Cloudera Manager Admin Console on page 17 the Home page displays.

Cloudera Manager Introduction | 19

Cloudera Manager Admin Console

Page 20: Cloudera Manager Intro

You can also navigate to the Home page by clicking Home in the top navigation bar.

The Home page has four tabs:

• Status - the default tab displayed when the Home page displays. It contains:

– A summary of the clusters being managed by Cloudera Manager.

To add a cluster, click and select Add Cluster and follow the instructions in Adding a Cluster.

Each cluster is represented in two panels: Status and Charts.

• Status - A table containing links to the All Hosts page and the status pages of the services runningin the cluster.

By default the tables are displayed expanded. To collapse a table, click . To expand a table, click .

Each service row in the table has a menu of actions that you select by clicking and can contain oneor more of the following indicators:

DescriptionMeaningIndicator

Indicates that the service has at least one health issue. The coloredbadge shows the number of health issues at the highest severity level.

Health Issue,

If there are Bad heath test results, the indicator has a red badge. Ifthere are no Bad health test results, but Concerning test results exist,then the badge is yellow. No indicator is shown if there are no Bad orConcerning health test results.

20 | Cloudera Manager Introduction

Cloudera Manager Admin Console

Page 21: Cloudera Manager Intro

DescriptionMeaningIndicator

Important: If there is one Bad health test result and twoConcerning health results, there will be three health issues,but the badge will be .

Click the indicator to display the Health Issues pop-up dialog.

By default only Bad health test results are shown in the dialog. Todisplay Concerning health test results, click the Also show n concerningissue(s) link. Click the link to display the Status page containing withdetails about the health test result.

Indicates that the service has at least one configuration issue. Thecolored badge shows the number of configuration issues at the highest

ConfigurationIssue,

severity level. If there are configuration errors, the indicator has a redbadge. If there are no errors but configuration warnings exist, then thebadge is yellow. No indicator is shown if there are no configurationnotifications.

Important: If there is one configuration error and twoconfiguration warnings, there will be three configurationissues, but the badge will be .

Click the indicator to display the Configuration Issues pop-up dialog.

By default only notifications at the Error severity level are listed,grouped by service name are shown in the dialog. To display Warningnotifications, click the Also show n warning(s) link. Click the messageassociated with an error or warning to be taken to the configurationproperty for which the notification has been issued where you canaddress the issue. See Configuring and Managing Services.

Indicates that at least one of a service's roles is running with aconfiguration that does not match the current configuration settingsin Cloudera Manager.

ConfigurationModified

Click the indicator to display the Outdated Configuration pop-up dialog.To remove the indicator, follow the instructions in ModifyingConfiguration Settings.

• Charts - A set of charts (view) that summarizes cluster level resource utilization (IO, CPU usage) andprocessing metrics.

By default the charts for each cluster are displayed expanded. To collapse a cluster's charts, click .To expand a a cluster's charts, click .

Click a chart to expand it into a full-page view with a legend for the individual charted entities as wellmore fine-grained axes divisions.

By default the time scale of a view is one day. To change the time scale, click a duration link

at the top-right of the view.

Note: The time scale applies to the charts across all clusters.

Cloudera Manager Introduction | 21

Cloudera Manager Admin Console

Page 22: Cloudera Manager Intro

To set the view type, click and select one of the following:

• Custom - displays the Custom view.• Default - displays the Default view.• Reset - resets the Custom view to the predefined set of charts, discarding any customizations.

– A table containing a link to the Cloudera Manager Services. The Cloudera Manager Services table has a

menu of actions that you select by clicking .

• All Health Issues - Displays all health issues by cluster. The colored badge has the same semantics as theper service health issues reported on the Status tab.

– By default only Bad health test results are shown in the dialog. To display Concerning health test results,click the Also show n concerning issue(s) link.

– To group the health test results by entity or health test, click the buttons on the Organize byEntity/Organize by Health Test toggle.

– Click the link to display the Status page containing with details about the health test result.

• All Configuration Issues - Displays all configuration issues by cluster. The colored badge has the samesemantics as the per service configuration issues reported on the Status tab. By default only notificationsat the Error severity level are listed, grouped by service name are shown in the dialog. To display Warningnotifications, click the Also show n warning(s) link.Click the message associated with an error or warning tobe taken to the configuration property for which the notification has been issued where you can address theissue.

• All Recent Commands - Displays all commands run recently across the clusters. A blue badge indicateshow many recent commands are still running. Click the command link to display details about the commandand child commands. See also Viewing Running and Recent Commands.

22 | Cloudera Manager Introduction

Cloudera Manager Admin Console

Page 23: Cloudera Manager Intro

Cloudera Manager API

The Cloudera Manager API provides configuration and service life cycle management, service health informationand metrics, and allows you to configure Cloudera Manager itself. The API is served on the same host and portas the Cloudera Manager Admin Console on page 17, and does not require an extra process or extra configuration.The API supports HTTP Basic Authentication, accepting the same users and credentials as the Cloudera ManagerAdmin Console.

This chapter contains an example of how to access the API:

• Using the Cloudera Manager Java API for Cluster Automation on page 23

Here are some additional resources for your exploration:

• Cloudera Manager API documentation• Cloudera Manager API tutorial• Cloudera Manager API client library (with example scripts). Here you can also find a Nagios monitoring script

that integrates with the API to discover the entities in the cluster and their health.

Using the Cloudera Manager Java API for Cluster AutomationOne of the complexities of Apache Hadoop is the need to deploy clusters of servers, potentially on a regularbasis. At Cloudera, which at any time maintains hundreds of test and development clusters in differentconfigurations, this process presents a lot of operational headaches if not done in an automated fashion. Thistopic describes an approach to cluster automation that works for us, as well as many of our customers andpartners.

Cluster Automation Use Cases

At Cloudera engineering, we have a big support matrix: We work on many versions of CDH (multiple releasetrains, plus things like rolling upgrade testing), and CDH works across a wide variety of OS distributions (RHEL5 & 6, Ubuntu Precise & Lucid, Debian Squeeze, and SLES 11), and complex configuration combinations — highlyavailable HDFS or simple HDFS, Kerberized or non-secure, using YARN or MR1 as the execution framework, andso on. Clearly, we need an easy way to spin-up a new cluster that has the desired setup, which we cansubsequently use for integration, testing, customer support, demos, and so on.

This concept is not new; there are several other examples of Hadoop cluster automation solutions. For example,Yahoo! has its own infrastructure tools, and you can find publicly available Puppet recipes, with various degreesof completeness and maintenance. Furthermore, there are tools that work only with a particular virtualizationenvironment. However, we needed a solution that is more powerful and easier to maintain.

Cloudera's automation system for Hadoop cluster deployment provisions VMs on-demand in our internal cloud.As cool as that capability sounds, it's actually not the most interesting part of the solution. More important isthat we can install and configure Hadoop according to precise specifications using a powerful yet simpleabstraction — using Cloudera Manager's open source REST API.

This is what our automation system does:

1. Installs the Cloudera Manager packages on the cluster.2. Starts the Cloudera Manager server.3. Uses the API to add hosts, install CDH, and define the cluster and its services.

Cloudera Manager Introduction | 23

Cloudera Manager API

Page 24: Cloudera Manager Intro

4. Uses the API to tune heap sizes, set up HDFS HA, turn on Kerberos security and generate keytabs, customizeservice directories and ports, and so on. Every configuration available in Cloudera Manager is exposed in theAPI.

The end result is a system that has become an indispensable part of our engineering process. The API also givesaccess to management features, such as gathering logs and monitoring information, starting and stoppingservices, polling cluster events, and creating a disaster recovery replication schedule. For example, the API canbe used to retrieve logs from HDFS, HBase, or any other service,without needing to know about different loglocations. The API can be used to stop any service, without worrying about any additional steps. (HBase needsto be gracefully shutdown.) We use these features extensively in our automated tests. As Cloudera Manageradds support for more services, their setup flows are the same as the existing ones.

Many of our customers and partners have also adopted the Cloudera Manager API for cluster automation:

• Some OEM and hardware partners, delivering Hadoop-in-a-box appliances, use the API to set up CDH andCloudera Manager on bare metal in the factory.

• Some of our high-growth customers are constantly deploying new clusters, and have automated that witha combination of Puppet and the Cloudera Manager API. Puppet does the OS-level provisioning, and thesoftware installation. After that, the Cloudera Manager API sets up the Hadoop services and configures thecluster.

• Others have found it useful to integrate the API with their reporting and alerting infrastructure. An externalscript can poll the API for health and metrics information, as well as the stream of events and alerts, to feedinto a custom dashboard.

Java API Examples

This example covers the Java API client. (Although Cloudera's internal automation tool uses the Python clienttoday, we plan to move to Java to better work with our other Java-based tools like jclouds.)

To use the Java client, add this dependency to your project's pom.xml:

<project><repositories><repository><id>cdh.repo</id><url>https://repository.cloudera.com/content/groups/cloudera-repos</url><name>Cloudera Repository</name>

</repository>…

</repositories><dependencies><dependency><groupId>com.cloudera.api</groupId><artifactId>cloudera-manager-api</artifactId><version>4.6.2</version> <!-- Set to the version you use -->

</dependency>…

</dependencies>...

</project>

The Java client works like a proxy. It hides from the caller any details about REST, HTTP, and JSON. The entrypoint is a handle to the root of the API:

RootResourceV4 apiRoot = newClouderaManagerClientBuilder().withHost("cm.cloudera.com").withUsernamePassword("admin", "admin").build().getRootV4();

From the root, you can traverse down to all other resources. (It's called "V4" because the currently ClouderaManager API version is version 4, but the same builder also returns a V1, V2, or V3 root.) Here is the tree viewof some of the key resources and the interesting operations they support:

24 | Cloudera Manager Introduction

Cloudera Manager API

Page 25: Cloudera Manager Intro

• RootResourceV4

– ClustersResourceV4 - host membership, start cluster

– ServicesResourceV4 - configuration, get metrics, HA, service commands

– RolesResource - add roles, get metrics, logs– RoleConfigGroupsResource - configuration

– ParcelsResource - parcel management

• HostsResource - host management, get metrics• UsersResource - user management

Of course, these are all documented in the Javadoc, and API documentation. To give a short concrete example,here is the code to list and start a cluster:

// List of clustersApiClusterList clusters =apiRoot.getClustersResource().readClusters(DataView.SUMMARY);for (ApiCluster cluster : clusters) {LOG.info("{}: {}", cluster.getName(), cluster.getVersion());

}

// Start the first clusterApiCommand cmd =apiRoot.getClustersResource().startCommand(clusters.get(0).getName());while (cmd.isActive()) {

Thread.sleep(100);cmd = apiRoot.getCommandsResource().readCommand(cmd.getId());

}LOG.info("Cluster start {}", cmd.getSuccess() ? "succeeded" : "failed " +cmd.getResultMessage());

To see a full example of cluster deployment using the Java client, see whirr-cm. Specifically, jump straight toCmServerImpl#configure to see the core of the action.

You may find it interesting that the Java client is maintained with very little effort. Using Apache CXF, the clientproxy comes free. It figures out the right HTTP call to make by inspecting the JAX-RS annotations in the RESTinterface, which is the same interface used by the Cloudera Manager API server. Therefore, new API methodsare available to the Java client automatically.

Cloudera encourages you to try the Cloudera Manager API, and post your questions and feedback on the ClouderaManager forums.

Cloudera Manager Introduction | 25

Cloudera Manager API

Page 26: Cloudera Manager Intro
Page 27: Cloudera Manager Intro

Cloudera Manager Guides

The following guides are included in the Cloudera Manager documentation set:

DescriptionGuide

These release notes provide information on the new features and knownissues and limitations for Cloudera Manager.Cloudera Manager Release Notes

This guide provides a comprehensive introduction to Cloudera Manager.Cloudera Manager Introduction

This guide explains how to install Cloudera Manager and CDH. ClouderaManager 4 supports managing CDH3 and CDH4.

Cloudera Manager Installation Guide

This guide is for Apache Hadoop developers and system administratorswho want to use the Cloudera Manager Admin Console to change CDH

Managing Clusters with ClouderaManager

configuration settings, add new services, add new clusters, add hosts toexisting clusters, upgrade your CDH or component versions, configureHigh Availability, and other similar functions.

This guide is for Apache Hadoop developers and system administratorswho want to use Cloudera Manager to monitor and diagnose their CDH

Cloudera Manager Monitoring andDiagnostics Guide

installation. You can use the Cloudera Manager Admin Console to monitorcluster usage, activities, and health, and view status and logs totroubleshoot problems.

• Introduction• Monitoring Services• Monitoring Hosts• Monitoring Activities• Logs• Events• Alerts• Reports• Charting Time-Series Data• Troubleshooting Cluster Configuration and Operation

This guide provides information on metrics supported by ClouderaManager.

Cloudera Manager Metrics

This guide is for system administrators who need to manage a ClouderaManager server installation. This guide covers adding and managing

Cloudera Manager AdministrationGuide

Cloudera Manager users, adding or upgrading licenses, configuring TLSsecurity, configuring the Alert Publisher, and other similar features.

Cloudera Manager Introduction | 27

Cloudera Manager Guides

Page 28: Cloudera Manager Intro

DescriptionGuide

This guide describes Cloudera Backup and Disaster Recovery (BDR), aseparately-licensed Cloudera product that provides an integrated,

Cloudera Backup and DisasterRecovery

easy-to-use management solution for enabling data protection in theHadoop platform.

This guide describes how to use Cloudera Manager to automate many ofthe manual tasks of implementing Kerberos security on your CDH cluster.

Configuring Hadoop Security withCloudera Manager

28 | Cloudera Manager Introduction

Cloudera Manager Guides

Page 29: Cloudera Manager Intro

Cloudera Manager Frequently Asked Questions

This guide answers frequently asked questions about Cloudera Manager.

General Questions

What are the new features of Cloudera Manager 4.7?

For a list of new features in Cloudera Manager 4.7, see New Features in Cloudera Manager 4.

What operating systems are supported?

See Requirements for Cloudera Manager for more detailed information on which platforms are supported.

What database platforms are supported?

See Requirements for Cloudera Manager for more detailed information on which database systems are supported.

What are the differences between the Standard and the Enterprise Versions of Cloudera Manager?

Cloudera Standard includes a free version of the commercially-available Cloudera Manager product. Both theStandard and Enterprise versions automate the installation, configuration, and monitoring of CDH3 or CDH4 onan entire cluster. Cloudera Enterprise provides additional functionality.

The full-featured version of Cloudera Manager is available as part of the Cloudera Enterprise subscription offering,and requires a license.

See the matrix at What are the Differences Between the Cloudera Standard and Enterprise Versions? for acomparison of the two versions. You can also view a discussion of the differences athttp://www.cloudera.com/content/cloudera/en/products/cloudera-manager.html.

If you are not an existing Cloudera customer, contact Cloudera Sales for information about obtaining thefull-featured version of Cloudera Manager.

If you are already a Cloudera customer and you need to upgrade the from Cloudera Standard to ClouderaEnterprise, contact Cloudera Support to obtain a license.

What version of CDH is required for Cloudera Manager 4.7?

See Requirements for Cloudera Manager for detailed information.

Can I upgrade CDH using Cloudera Manager?

Yes, as of Cloudera Manager 4.5 you can upgrade to CDH4.1.2 or later from within the Cloudera Manager AdminConsole using parcels. Furthermore, once you have installed or upgraded CDH using parcels, you can performrolling upgrades on your CDH services. If you have HDFS High Availability configured and enabled, you can performa rolling upgrade on your cluster without taking the entire cluster down.

Cloudera Manager Introduction | 29

Cloudera Manager Frequently Asked Questions

Page 30: Cloudera Manager Intro

Important: Cloudera Manager version 3.x and CDH3 have reached End of Maintenance (EOM) as ofJune 20, 2013. Cloudera will not support or provide patches for any of the Cloudera Manager version3.x and CDH3 releases. Even though Cloudera Manager 4.x will continue to support CDH3, it is stronglyrecommended that you upgrade to CDH4. See Upgrading existing installations of CDH3 to CDH4 formore details.

For instructions on upgrading CDH4 to a newer version, see Upgrading to the Latest Version of CDH4 in a ClouderaManager Deployment. For instructions on upgrading from CDH3 to CDH4, see Upgrading CDH3 to CDH4 in aCloudera Manager Deployment.

What version of CDH does Cloudera Manager 4.7 install?

Cloudera Manager 4.7 allows you to install any version of CDH3 or CDH4.

What upgrade paths are available for Cloudera Manager, and what's involved?

For instructions about upgrading, see Upgrading Cloudera Manager.

How do I install Cloudera Manager 4.7 in a walled-off environment (no Internet access)?

You can set up a local repository and use it in the installer. For instructions, see Appendix A - UnderstandingCustom Installation Solutions.

Do slave nodes need access to the Cloudera public repositories for an install with Cloudera Manager?

As of Cloudera Manager 4.5, you can perform an installation or upgrade using the new parcel format. Whenusing parcels, only the Cloudera Manager server requires access to the Cloudera public repositories. Distributionof the parcels to slave nodes is done between the Cloudera Manager server and the slave nodes. See UsingParcels for more information. If you want to install using the traditional packages, nodes only require access tothe installation files.

For both parcels and packages, it is also possible to create local repositories that serve these files to the nodesthat are being upgraded. If you have established local repositories, no access to the Cloudera public repositoryis required. For more information, see Creating and Using your own Repository.

Can I use the Service Monitoring features of Cloudera Manager without using Service and ConfigurationManagement?

No. To understand the desired state of the system, we need the global configuration that the service managementfeature of Cloudera Manager gathers and provides. The Cloudera Manager agent doubles as both the agent forsupervision and for monitoring.

Can I run the Cloudera Management services and the Hadoop services on the host where the Cloudera ManagerServer is running?

Yes. This is especially common in deployments that have a small number of hosts.

Which sudo commands does Cloudera Manager run?

The sudo commands are:

• yum (Red Hat/CentOS/Oracle)• zypper (SLES)• apt-get (Debian/Ubuntu)• apt-key (Debian/Ubuntu)• sed

• service

30 | Cloudera Manager Introduction

Cloudera Manager Frequently Asked Questions

Page 31: Cloudera Manager Intro

• /sbin/chkconfig (Red Hat/CentOS/Oracle)• /usr/sbin/update-rc.d (Debian/Ubuntu)• id

• rm

• mv

• chown

• install

Does Cloudera Manager Support an API?

Yes. A comprehensive set of APIs for the various features is supported in this version of Cloudera Manager. Formore information about the Cloudera Manager API, see Cloudera Manager API on page 23. You can downloadthis Cloudera Manager API example that shows how to integrate with Nagios or other systems.

Using Cloudera Manager

How do I set the rack topology script?

Cloudera Manager includes internal rack awareness scripts, but you must specify the racks where the hosts inyour cluster are located. If your cluster contains more than 10 hosts, Cloudera recommends that you specify therack for each host. HDFS and MapReduce will automatically use the racks you specify. For instructions, seeSpecifying the Racks for Hosts.

How do I configure my daemons to use a custom GC parameter?

Every Java-based role in Cloudera Manager has a configuration setting called "Additional Java configurationoptions for <role>" where you can enter command line options. Commonly, garbage collection flags or extradebugging flags would be passed here.

To find the appropriate configuration setting, select the service you want to modify in the Cloudera Manager UI,then use the keyword search to search for the Additional Java configuration options.

You can add configuration options for all instances of a given role by making this configuration change at theService level. For example, to modify the setting for all DataNodes, select the HDFS service, then modify the"Additional Java configuration options for DataNode" setting).

To modify a configuration option for a given instance of a role, select the service, then select the particular roleinstance (e.g. a specific DataNode) you want to modify. The configuration settings you modify will apply to theselected role instance only.

For detailed instructions see the Modifying Service Configurations section of Managing Clusters with ClouderaManager.

Cloudera Manager Introduction | 31

Cloudera Manager Frequently Asked Questions

Page 32: Cloudera Manager Intro
Page 33: Cloudera Manager Intro

Getting Help and Support

Cloudera Manager documentation is available under the Support menu in the Cloudera Manager Admin console.In addition there are several other channels to obtain help with and information about Cloudera Manager.

Community SupportAny user of Cloudera Manager (Standard or Enterprise), can get help through community user groups:

• Cloudera Manager Users group• CDH Users group

As a Cloudera Manager Standard user, you can also access the Cloudera Manager support mailing list fromwithin the Cloudera Manager Admin console by selecting Support > Mailing List .

Cloudera Enterprise SupportCloudera can help you install, configure, optimize, tune, and run Hadoop for large scale data processing andanalysis. Cloudera supports Hadoop whether you run our distribution on servers in your own data center, or onhosted infrastructure services such as Amazon EC2, Rackspace, SoftLayer, or VMware vCloud.

If you are a Cloudera Enterprise customer, you can access the Cloudera Support Portal from within the ClouderaManager Admin console, by selecting Support > Cloudera Support Portal . From there you can:

• Create a Cloudera Support Ticket• Visit the Cloudera Knowledge Base• Learn how to register for an account to create a support ticket

Get Announcements about New CDH and Cloudera Manager ReleasesCloudera provides the following public mailing lists that send announcements about new CDH and ClouderaManager product releases and updates:

• To receive CDH release announcements, subscribe to the CDH-announce list.• To receive Cloudera Manager release announcements, subscribe to the CM-announce list.

Report IssuesCloudera tracks software and documentation bugs and enhancement requests for CDH on issues.cloudera.org.Your input is appreciated, but before filing a request, please search the Cloudera issue tracker for existing issuesand send a message to the CDH user's list, [email protected], or the CDH developer's list,[email protected].

Cloudera Manager Introduction | 33

Getting Help and Support

Page 34: Cloudera Manager Intro