http://www.aboutyun.com/thread-9189-1-1.html here to the hehe. 1. Related catalogue
/var/log/cloudera-scm-installer: Install log directory.
/var/log/*: Related log files (related services and cm).
/usr/share/cmf/: Program installation directory.
/usr/lib64/cmf/: Agent program code.
/var/lib/cloudera-scm-server-db/data: Embedded Database directory.
/usr/bin/postgres: Embedded Database program.
/etc/cloudera-scm-agent/: The configuration directory of the agent.
/etc/cloudera-scm-server/: The configuration directory of the server.
/opt/cloudera/parcels/: Hadoop-related Service installation directory.
/opt/cloudera/parcel-repo/: Downloaded service package data, data format is parcels.
/opt/cloudera/parcel-cache/: The downloaded service package caches data.
/etc/hadoop/*: Client configuration file directory.
2. Configuration
Hadoop configuration file
The configuration file is placed in the/var/run/cloudera-scm-agent/process/directory. such as:/var/run/cloudera-scm-agent/process/193-hdfs-namenode/core-site.xml. These profiles are generated when the appropriate service (such as HDFs) is started by Cloudera Manager, and the content is obtained from the database (that is, parameters configured through the interface).
Changing the configuration on the CM interface is not immediately reflected in the configuration file, which is stored in the database, and the configuration file is generated the next time the service is restarted. And a new profile is generated each time it is started.
The CM server primary database is configs for the data table configured in the SCM base. It contains the configuration information of the service, and each configuration change will add all the configuration contents of the current page to the database to save the configuration modification history.
The SCM database is configured to be accessible only from localhost, if you need to connect to this database externally, modify the vim/var/lib/cloudera-scm-server-db/data/pg_hba.conf file, and then restart the database. The user running the database is CLOUDERA-SCM.
View Configuration Contents
Query the contents of the Configs data table directly from the SCM database.
Access rest api:http://hostname:7180/api/v4/cm/deployment to return the JSON format deployment configuration information.
How to configure the build
CM generates a separate configuration directory (file) for each service process. All configurations unify the query database generation on the server (because the SCM database can only be accessed under localhost) to generate the configuration file, and the agent downloads the zip package containing the configuration files to the specified directory locally via the network.
Configuration modifications
CM is pre-defined for configurations that need to be modified, and is configured by using XML configuration fragments in Advanced configuration items for configurations that do not have a pre-defined configuration. For the configuration file under/etc/hadoop/is the configuration of the client, you can build the client configuration in cm by deploying the client.
3. Database
Cloudera Manager's main database is SCM, which stores the information needed for Cloudera Manager to run: Configuration, host, user, etc.
4. CM Structure
CM is divided into two parts of server and agent and database (with the changed embedded PostgreSQL). It mainly does three events:
Manage monitoring cluster hosts.
Unified management configuration.
Manage and maintain the Hadoop platform system.
Implementation of the C/s structure, the agent is responsible for the client to execute the service end of the command, the execution method is generally used to invoke the corresponding service shell script. The server side is the Java Rest Service, which provides the rest Api,web management side to invoke the server-side functionality through the rest API, and the Web interface uses rich-client technology (KNOCKOUT).
Server-side principals use Java implementations.
The agent-side body uses Python, the start of the service is initiated by invoking the appropriate shell script, and the startup script is repeated 4 times if the startup fails.
The agent and server keep the heartbeat, using the Thrift RPC framework.
5. Upgrade
In cm you can upgrade related services through the Interface Wizard. The upgrade process is three steps:
Download the service package.
Distribute the downloaded service packages to the managed machines in the cluster.
Install the service package and use the soft link to link the Service program directory to the newly installed package directory.
6. Uninstall
sudo/usr/share/cmf/uninstall-scm-express.sh, and then delete the/var/lib/cloudera-scm-server-db/directory, or the next installation may not be successful.
7. Turn on PostgreSQL remote access
The CM embedded database is configured to be accessible only from localhost, if you need to view the data externally, modify the vim/var/lib/cloudera-scm-server-db/data/pg_hba.conf file, and then restart the database. The user running the database is CLOUDERA-SCM.
Cloudera Directory Location
