Hortonworks Docs
»
ambari administration 2.7.5
»
Administering Ambari
Administering Ambari
Also available as:
Introducing Ambari administration
Understanding Ambari terminology
Using the Administrator role in Ambari Web
Log In to Ambari as administrator
Using the Ambari Admin page
Create a cluster
Using Ambari Blueprints
Export an Ambari Blueprint
Change the admin password
Changing your JDK
Move the ZooKeeper server
Rename a cluster
Register a remote cluster
Setting up Ambari to use an Internet proxy server
Configure Ambari server to use a proxy server
Configure yum to use Internet proxy settings
Managing cluster roles
Understanding cluster roles and access
Role based access control
Modify access levels for users and groups
Managing versions
Register a new version
Update version repository base urls
De-register a version
Managing local users
Manage privileges for local and ldap users
Create a local user
Set user status
Grant Ambari admin privileges
Configure password policy for users
Change the password for a local user
Delete a local user
Enable user home directory creation
Managing local group membership
Understanding group types
Modify group membership
Create a local group
Delete a local group
Installing Ambari agents manually
Download the Ambari repository on RHEL-CentOS-Oracle Linux 7
Install the Ambari agents manually on RHEL-CentOS-Oracle 7
Download the Ambari repository on Amazon Linux 2
Install the Ambari agents manually on Amazon Linux 2
Download the Ambari repository on SLES 11
Install the Ambari agents manually on SLES 11
Download the Ambari repository on SLES 12
Install the Ambari agents manually on SLES 12
Download the Ambari repository on Ubuntu 16
Install the Ambari agents manually on Ubuntu 16
Download the Ambari repository on Debian 9
Install the Ambari agents manually on Debian 9
Understanding service users and groups
Default user accounts
Default group accounts
Setting properties that depend on service or group user names
Understanding custom and private host names
Using custom and private host names
Configure a public host name
Configure a custom host name
Public host name limitations
Verifying public host name configuration
Changing host names
Moving the Ambari server
Back up current Ambari database
Update all Ambari agents
Install the new Ambari server
Populate the new Ambari database
Start the new Ambari server and agents
Configuring LZO compression
Enable LZO compression
Configure core-site.xml for LZO
Optional - Enable LZO using Ambari Blueprints
Disable automatic LZO library download and installation
Manually installing LZO libraries
Manually installing LZO on RHEL-CentOS-Oracle
Manually Installing LZO on SUSE Linux
Manually installing LZO on Ubuntu or Debian
Using LZO compression with Hive queries
Create LZO files
Write custom Java to create LZO files
Using an existing or installing a default database
Using an existing database with Ambari
Using Ambari with Oracle
Using Ambari with MySQL or MariaDB
Using Ambari with PostgreSQL
Using a new or existing database with Hive
Using Hive with Oracle
Using Hive with MySQL
Using Hive with PostgreSQL
Using an existing database with Oozie
Using Oozie with Oracle
Using Oozie with MySQL
Using Oozie with PostgreSQL
Example: Install MariaDB for use with multiple components
Configuring network port numbers
Default network port numbers for Ambari
Change the default Ambari server port
Change the default Ambari server-agent port
Tuning Ambari performance
Adjust Ambari server heap size
Increase Ambari server cache size
Adjust jdbc connection pool settings
Increase MySQL wait_timeout and interactive_timeout settings
Purge Ambari server database history
Optimize Ambari agent performance
Customizing Ambari log and pid directories
Finding Ambari log files
Configure Ambari logging level
Customizing Ambari agent log and pid directories
Managing host participation for HDFS and YARN
Ambari-managed host participation
Enable manage.include.files for HDFS
Enable manage.include.files for Yarn
Disable manage.include.files for HDFS
Disable manage.include.files for Yarn
De-register a version
Use
Admin/Versions
to de-register a selected stack version.
Browse to
Ambari Admin
>
Versions
.
If necessary, click
Manage Versions
, then
OK
.
Click the version you want to de-register.
Only versions that are not installed in a cluster can be de-registered.
Click
De-register Version
and then confirm.
Parent topic:
Managing versions
© 2012–2019, Hortonworks, Inc.
Document licensed under the
Creative Commons Attribution ShareAlike 4.0 License
.
Hortonworks.com
|
Documentation
|
Support
|
Community